Celestin Apprentice 5/Apprentice-Release5.iso/Information/THINK C Digest/1993/93-04

Text File | 1995-12-31 | 138KB | 3,551 lines

Path: ucivax!gateway
From: [e-mail] (Douglas Yarrington)
Subject: After Dark Dev
Message-ID: <[e-mail]>
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: fa.think-c
Lines: 18
Date: 1 Apr 93 05:40:28 GMT

Hello.

I've had some inspiration of late to produce an After Dark screen saver
module that will, hopefully, represent some of my experiences in Japan: for
example, no one here really understands what the "Mowin' Man" is. So I'd
like to give them something.

Can someone tell me where the After Dark dev kit is these days? Times were
it used to be on ftp sites. Has Berkely Systems removed this from pd? If
so, how do I obtain a dev kit for ThinkC.

Thanks.

--douglas

  Douglas Yarrington                                 [e-mail]
  IBS Systems - Digital Design                             Flat Antenna Stuff
  Matsushita Electric Works, Ltd        "A beautiful place to be for a while"










Path: ucivax!gateway
From: [e-mail] (Aaron Barnett)
Subject: assembly books
Message-ID: <[e-mail]>
Content-transfer-encoding: 7BIT
MIME-version: 1.0
Newsgroups: fa.think-c
X-VMS-To: THINK
Lines: 3
Date: 1 Apr 93 17:52:43 GMT
X-Envelope-to: [e-mail]

can anyone recomend a good book/reference on 68xxx assembly?

aaron










Path: ucivax!gateway
From: [e-mail] ("The sky is ecstasy dancing...")
Subject: Control icons in a standard window.
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 20
Date: 1 Apr 93 18:43:25 GMT
X-Vmsmail-To: SMTP%"[e-mail]"

Hi,
   I am trying to add controls to a window, and am not being very successful.
What I would like to do is use icons as push buttons.  The way that I am
currently doing this is to record were the rect of the icon is located on the
window, and then check to see if the mouse was clicked on that rect.

   Since these are controls, I would like to add them to the control list of the
window, and deal with them through FindControl etc.  What I was wondering is,
is there an easier way of doing this than creating my own control definitions,
or if creating a control definition is the only way, would someone send me an
example, cause I am failing miserably at figuring out how to create one.

Thanks,
  Mike

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[e-mail]        Loose cannon and programmer of Vaxes
[e-mail]    I don't work for anybody, so I don't
[e-mail]        need a disclaimer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










Path: ucivax!gateway
From: [e-mail] (Jeff Garner)
Subject: Finding Mac's Name.
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Newsgroups: fa.think-c
Lines: 16
Date: 2 Apr 93 00:16:43 GMT


I'd like to find the name of the Mac, as specified in the Sharing Setup
control panel.  I'd prefer not using an AppleTalk command, since AppleTalk
could be off during the program's use.

I've looked in IM VI, New TNs, CSMP digests, and other places...

I know where the info gets stored... in the Users & Groups Data File in
the Prefs folder...  but surely there's an easier way than hacking the
data file!

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jeff Garner     Shoestring Software Products   [e-mail]
[phone]   Mercer Island, Washington     [e-mail]












Path: ucivax!gateway
From: [e-mail] (Pete Resnick)
Subject: Re: Finding Mac's Name.
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>; from "Jeff Garner" at Apr 2, 93 12:16 am
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: fa.think-c
Lines: 13
Date: 2 Apr 93 02:54:51 GMT

> I'd like to find the name of the Mac, as specified in the Sharing Setup
> control panel.  I'd prefer not using an AppleTalk command, since AppleTalk
> could be off during the program's use.

See IM VI, p. 13-15. It's System 'STR ' resource -16413. It's also in
the "What's New With AppleTalk Phase 2" Tech note.

pr
--
Pete Resnick             (...so what is a mojo, and why would one be rising?)
Graduate assistant - Philosophy Department, Gregory Hall, UIUC
System manager - Cognitive Science Group, Beckman Institute, UIUC
Internet: [e-mail]










Path: ucivax!gateway
From: [e-mail] (Kevin Quick)
Subject: List Manager
Via: uk.ac.open; Fri, 2 Apr 1993 15:25:37 +0100
X-Sender: kc_quick@sunflower
Message-ID: <[e-mail]>
X-Mailer: Eudora 1.3.1
Newsgroups: fa.think-c
Lines: 11
Date: 2 Apr 93 14:27:43 GMT

Does anybody have some example code in TC for calling the list manager to
set up a new list.

Thanks in Advance.

Kevin Quick
Computer Support Engineer
The Open University

Mail by Eudora 1.3











Path: ucivax!gateway
From: [e-mail] (Gary Hurtz)
Subject: I want out of the mailing list
Message-ID: <[e-mail]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Newsgroups: fa.think-c
Lines: 8
Date: 2 Apr 93 17:50:04 GMT

I tried mailing the address that was given out last week, but im still not
off of the list.  I dont have that address anymore, so sorry I had to do
it this way.

please remove me, [e-mail]













Path: ucivax!gateway
From: [e-mail] (Apex Voice Communications)
Subject: Take my address off the mail list
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 5
Date: 2 Apr 93 23:48:46 GMT


Please take me off of the think c list.

[e-mail]











Path: ucivax!gateway
From: [e-mail] (Jean-Marie Laborde)
Subject: Code for Error String 1 (at last)
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 243
Date: 5 Apr 93 06:01:29 GMT

Here is code for ErrorStrings I promissed last month.
Please excuse the delay due to too much work (but is not very specific).

The stuff has 2 parts,
o------one is the code of 3 functions message(), FiltreDial() and
extraction_texte_erreur()
contained in the file message.c transmitted separately;

0-----the other is this message containing a text description of the required
resource file, to be SAResed.

I did not incorporated the 28K string to this message.r because the
corresponding
file would have been huge (142K), so after recompiling the resource
and obtained a message.rsrc file you should add to it the TEXT resource with
ID 128
containing the chain at the end of this message and starting with

DS Table
1     dsBusError - bus error
2     dsAddressErr - address error
3     dsIllInstErr - illegal instruction error

end ending with

Primary or Secondary Init Code
-32768 svTempDisable - Temporarily disable card but run primary init
-32640 svDisabled - Reserve -32640 to -32768 for Apple temp disables

Next is a sample code to test message():
****************************************************************************
OSErr   myOSErr;
void    message(char *chaine,...);

void main()
{
        InitGraf(&thePort);
        InitWindows();
        InitFonts();
        InitDialogs(0L);
        InitCursor();
        TEInit();

        PrintErr=0;             /* an alternative solution is a call of type
PrOpen();PrClose();
                                           instead of PrintErr=noErr;
//noErr==0 */

        {
                long longint=1234567890;
                char mychar='a';
                long lgchar='APPL';

                myOSErr=1;
                message("%err with context\nvalue of longint is %ld\nvalue of mychar is %c\nvalue of lgchar is %lc",longint,mychar,lgchar);
        }
}
****************************************************************************


The way to use the stuff can be found at the beginning of the file message.c
The way to recompile the resource using SARez is the following:
        -start SARez
        -click the pull-down menu rez.out and choose "Write output to a new
file"
                        give the name message.rsrc for the new file
        -enter rsrc for the Type (default APPL)
        -enter RSED for the Creator (default ????)
        -if you do not use Resedit, but e.g. Resorcerer, type RSRC and Doug
instead
        -Push the button Description files... and add the file
                message.r to the list of description file
        -Push the button #include Paths... and add the folder RIncludes to
paths.
        -Press button SARez,   it should work.

Begin of the contents of the required text file message.r to run SARez:
/****************************************************************************/
resource 'DITL' (128) {
        {       /* array DITLarray: 4 elements */
                /* [1] */
                {60, 48, 82, 162},
                Button {
                        enabled,
                        "Resume"
                },
                /* [2] */
                {60, 196, 81, 306},
                Button {
                        enabled,
                        "ExitToShell()"
                },
                /* [3] */
                {60, 344, 80, 440},
                Button {
                        enabled,
                        "Debug"
                },
                /* [4] */
                {16, 20, 44, 463},
                UserItem {
                        enabled
                }
        }
};

resource 'DLOG' (128, "Message") {
        {40, 24, 134, 497},
        altDBoxProc,
        invisible,
        noGoAway,
        0x0,
        128,
        "OSEerr"
};

data 'TEXT' (128) {
        $"4453 2054 6162 6C65 0D31 2020 2020 2064"            /* DS TableB1
 d */
        /* .......... */
        $"6162 6C65 73"                                       /* ables */
};
/****************************************************************************/
end of the contain of file message.r to run SARez.

You finally need the 28K long chain giving the textual interpretation of
all the error codes.
Following is the begin and the end of it
/****************************************************************************/
DS Table
1     dsBusError - bus error
2     dsAddressErr - address error
3     dsIllInstErr - illegal instruction error
4     dsZeroDivErr - zero divide error
5     dsChkErr - check trap error
6     dsOvflowErr - overflow trap error
7     dsPrivErr - privilege violation error
8     dsTraceErr - trace mode error
9     dsLineAErr - line 1010 trap error
10    dsLineFErr - line 1111 trap error
11    dsMiscErr - miscellaneous hardware exception error
12    dsCoreErr - unimplemented core routine error
13    dsIrqErr - uninstalled interrupt error
14    dsIOCoreErr - IO Core Error
15    dsLoadErr - Segment Loader Error
16    dsFPErr - Floating point error
17    dsNoPackErr - package 0 not present [List Manager]
18    dsNoPk1 - package 1 not present [Reserved by Apple]
19    dsNoPk2 - package 2 not present [Disk Initialization]
20    dsNoPk3 - package 3 not present [Standard File]
21    dsNoPk4 - package 4 not present [Floating-Point Arithmetic]
22    dsNoPk5 - package 5 not present [Transcendental Functions]
23    dsNoPk6 - package 6 not present [International Utilities]
24    dsNoPk7 - package 7 not present [Binary/Decimal Conversion]
25    dsMemFullErr - out of memory!
26    dsBadLaunch - can't launch file
27    dsFSErr - file system map has been trashed
28    dsStknHeap - stack has moved into application heap
30    dsReinsert - request user to reinsert off-line volume
31    dsNotThe1 - not the disk I wanted (obsolete)
33    negZcbFreeErr - ZcbFree has gone negative
40    dsGreeting - welcome to Macintosh greeting
41    dsFinderErr - can't load the Finder error
42    dsBadStartupDisk - unable to mount boot volume (obsolete)
43    dsSystemFileErr - canUt find System file to open (obsolete)
51    dsBadSlotInt - unserviceable slot interrupt
81    dsBadSANEopcode - bad opcode given to SANE Pack4
83    dsBadPatchHeader - SetTrapAddress saw the Rcome-fromS header
84    menuPrgErr - happens when a menu is purged
85    dsMBarNFnd - SysErr -- cannot find MBDF
86    dsHMenuFindErr - SysErr -- recursively defined HMenus
87    dsWDEFnFnd - Could not load WDEF
88    dsCDEFnFnd - Could not load CDEF
89    dsMDEFnFnd - Could not load MDEF
90    dsNoFPU - FPU instruction executed, but machine has no FPU
98    dsNoPatch - Can't patch for particular Model Mac
99    dsBadPatch - Can't load patch resource
101   dsParityErr - memory parity error
102   dsOldSystem - System is too old for this ROM
103   ds32BitMode - booting in 32-bit on a 24-bit sys
104   dsNeedToWriteBootBlocks - need to write new boot blocks
105   dsNotEnoughRAMToBoot - need at least 1.5MB of RAM to boot 7.0
20000 dsShutDownOrRestart - user choice between ShutDown and Restart
20001 dsSwitchOffOrRestart - user choice between Switch off or Restart
20002 dsForcedQuit - allow the user to ExitToShell, return if Cancel

............
............
............

Mac TCP
-23000 ipBadLapErr - Bad network configuration
-23001 ipBadCnfgErr - Bad IP configuration error
-23002 ipNoCnfgErr - Missing IP or LAP configuration error
-23003 ipLoadErr - Error in MacTCP load
-23004 ipBadAddr - Error in getting address
-23005 connectionClosing - Connection in closing
-23006 invalidLength
-23007 connectionExists - Request conflicts with existing connection
-23008 connectionDoesntExist - Connection does not exist
-23009 insufficientResources - Insufficient rsrcs to perform request
-23010 invalidStreamPtr
-23011 streamAlreadyOpen
-23012 connectionTerminated
-23013 invalidBufPtr
-23014 invalidRDS
-23014 invalidWDS
-23015 openFailed
-23016 commandTimeout
-23017 duplicateSocket
-23030 ipOpenProtErr - Can't open new protocol, table full
-23031 ipCloseProtErr - Can't find protocol to close
-23032 ipDontFragErr - Packet too large to send w/o fragmenting
-23033 ipDestDeadErr - Destination not responding
-23034 ipBadWDSErr - Error in WDS format
-23035 icmpEchoTimeoutErr - ICMP echo timed-out
-23036 ipNoFragMemErr - No memory to send fragmented pkt
-23037 ipRouteErr - Can't route packet off-net
-23041 nameSyntaxErr
-23042 cacheFault
-23043 noResultProc
-23044 noNameServer
-23045 authNameErr
-23046 noAnsErr
-23047 dnrErr
-23048 outOfMemory

Font Manager
-32615 fontNotOutlineErr - bitmap passed, routine does outlines only

Primary or Secondary Init Code
-32768 svTempDisable - Temporarily disable card but run primary init
-32640 svDisabled - Reserve -32640 to -32768 for Apple temp disables
/****************************************************************************/

You can find the whole thing in the resource fork of a convenient DA called
SystemError.
If you have trouble in getting this I could e-mail you personally
this chain. Just ask for this...
Enjoy "Error Strings".

--
Jean-Marie LABORDE          [e-mail]   or   UUCP:  imag!laborde










Path: ucivax!gateway
From: [e-mail] (Jean-Marie Laborde)
Subject: Code for Error String (2)
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 137
Date: 5 Apr 93 06:09:51 GMT

/*code of 3 functions, message(), FiltreDial() and extraction_texte_erreur(),
needed to build the ErrorString feature, see other e-mail */
/***************************************************************
Copyright notice
) Jean-Marie Laborde LSD2-IMAG 1992-1993
This code can be freely distributed and used, subject solely to the
following conditions
        % do not distribute changed or amended versions without prior
agreement of the author.
        % do not remove the present copyright notice
This code is probably as any piece of code not absolutely bugfree and is
not guaranteed in any manner.

This code was developed at the University of Grenoble (France) in connection
with the project Cabri-gomtre.
Cabri-gomtre is an integrated project for the design of ITS in the domain of
Geometry.
It is based on a microworld for Euclidian geometry called Cabri-gomtre and
available from different distributors:
        in the US contact
                Brooks/Cole Pacific Grove, California 93950    1-(800) 354
9706
        outside the US contact
                Projet Cabri-gomtre, LSD2-IMAG        (33) 76 51 46 16
(fax [phone])
to obtain information about local distributors and publishers in other
countries

Please send comments and/or suggestions to the following address
        Jean-Marie Laborde
        Cabri-gomtre project
        LSD2-IMAG, Universit Joseph Fourier Grenoble
        Centre National de la Recherche Scientifique
        (33) 76 51 46 10    fax   [phone]
        [e-mail]


/***************************************************************

/*  % declare in your program a global myOSErr or any other suitable name  of
type OSErr;
the following #define makes the thing work */
#define MONERREUR       myOSErr

/*      %% put the following prototype where needed:
                        void    message(char *chaine,...);*/


/*  %%% make calls in your program of general type
                message("%err ResError %d ResErr=%d",MONERREUR,ResErr);

                -the simplest possible call is simply of type   message("any
C-string");

        and then        message("");

                -each time message() is called it checks if MONERREUR!=noErr
                as well as checking all the standard managers to detect any
                abnormal condition involving
                                the Resource Manager    (global ResErr
 via ResError()),
                                the System
(global DSErrCode   via SysError()),
                                the Memory Manager              (global MemErr
        via MemError()),
                                the Print Manager               (global
PrintErr        via PrError()).
                In such a case a dialog prompts with the corresponding error
string(s) in a list
                with 3 buttons:
                        % Resume                => resumes execution
                        % ExitToShell   => just exits to shell
                        % Debug                 => enters the Debugger (If the
Think C Debugger is present
we land in the code of the message() function, it is likely you will type
'command'-o)

                If no abnormal condition, message() shows the string given as
first argument CHAIN
                unless CHAIN starts with %err. In that case message() simply
returns and
                the call is absolutely transparent to the user.

                In addition, using a pattern close to formatted output, you
can output values
in the CHAIN taking advantage of the special character %:
Suppose
                        myOSErr has value 1  (Bus Error),
                        long int longint has value 1234567890,
                        char mychar has value 'a',
                        long char lgchar has value 'APPL',
then the following statement
                        message("%err with context\nvalue of longint is %ld\n    value of mychar is %c\nvalue of lgchar is %lc",longint,mychar,lgchar);
will produce following output:

_________________________________________________________
                        |
                                                        |
                        |       Error MONERREUR: 1 (dsBusError - bus error)
                |
                        |       with context
                                        |
                        |       value of longint is 1234567890
                        |
                        |           value of mychar is 'a'
                                |
                        |       value of lgchar is 'APPL'
                                |
                        |       __________              _________________
        _________       |
                        |       | Resume |              | ExitToShell() |
        | Debug |       |
                        |       __________              _________________
        _________       |

_________________________________________________________ .

In CHAIN '\n' or '\r' works the same.

% when if %err, %ld, %d, %f, %s, %lc or %c      has following interpretation

                                %err =>         makes the call transparent if
noErr and CHAIN starts with %err
                                %ld                     output for a long int
                                %d                      output for a int
                                %f                      output for a float
(ev. double)
                                %s                      output for a C-string
                                %lc                     output for a long to
be printed as 'APPL'
                                %c                      output for a character
                (7(BEL) => \a,  8(BS) => \b,  9(HT) => \t, 10(LF) => \n,
                 11(VT) => \v, 12(FF) => \f, 13(CR) => \r), 127 => '(dec 127)'


--
Jean-Marie LABORDE          [e-mail]   or   UUCP:  imag!laborde










Path: ucivax!gateway
From: [e-mail] (Jean-Marie Laborde)
Subject: Code for Error String (2)
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 121
Date: 5 Apr 93 06:30:10 GMT

/*code of 3 functions, message(), FiltreDial() and extraction_texte_erreur(),
needed to build the ErrorString feature, see other e-mail */
/***************************************************************
Copyright notice
) Jean-Marie Laborde LSD2-IMAG 1992-1993
This code can be freely distributed and used, subject solely to the
following conditions
        % do not distribute changed or amended versions without prior
agreement of the author.
        % do not remove the present copyright notice
This code is probably as any piece of code not absolutely bugfree and is
not guaranteed in any manner.

This code was developed at the University of Grenoble (France) in connection
with the project Cabri-gomtre.
Cabri-gomtre is an integrated project for the design of ITS in the domain of
Geometry.
It is based on a microworld for Euclidian geometry called Cabri-gomtre and
available from different distributors:
        in the US contact
                Brooks/Cole Pacific Grove, California 93950    1-(800) 354
9706
        outside the US contact
                Projet Cabri-gomtre, LSD2-IMAG        (33) 76 51 46 16
(fax [phone])
to obtain information about local distributors and publishers in other
countries

Please send comments and/or suggestions to the following address
        Jean-Marie Laborde
        Cabri-gomtre project
        LSD2-IMAG, Universit Joseph Fourier Grenoble
        Centre National de la Recherche Scientifique
        (33) 76 51 46 10    fax   [phone]
        [e-mail]


/***************************************************************

/*  % declare in your program a global myOSErr or any other suitable name  of
type OSErr;
the following #define makes the thing work */
#define MONERREUR       myOSErr

/*      %% put the following prototype where needed:
                        void    message(char *chaine,...);*/


/*  %%% make calls in your program of general type
                message("%err ResError %d ResErr=%d",MONERREUR,ResErr);

                -the simplest possible call is simply of type   message("any
C-string");

        and then        message("");

                -each time message() is called it checks if MONERREUR!=noErr
                as well as checking all the standard managers to detect any
                abnormal condition involving
                                the Resource Manager    (global ResErr
 via ResError()),
                                the System
(global DSErrCode   via SysError()),
                                the Memory Manager              (global MemErr
        via MemError()),
                                the Print Manager               (global
PrintErr        via PrError()).
                In such a case a dialog prompts with the corresponding error
string(s) in a list
                with 3 buttons:
                        % Resume                => resumes execution
                        % ExitToShell   => just exits to shell
                        % Debug                 => enters the Debugger (If the
Think C Debugger is present
we land in the code of the message() function, it is likely you will type
'command'-o)

                If no abnormal condition, message() shows the string given as
first argument CHAIN
                unless CHAIN starts with %err. In that case message() simply
returns and
                the call is absolutely transparent to the user.

                In addition, using a pattern close to formatted output, you
can output values
in the CHAIN taking advantage of the special character %:
Suppose
                        myOSErr has value 1  (Bus Error),
                        long int longint has value 1234567890,
                        char mychar has value 'a',
                        long char lgchar has value 'APPL',
then the following statement
                        message("%err with context\nvalue of longint is %ld\n    value of mychar is %c\nvalue of lgchar is %lc",longint,mychar,lgchar);
will produce following output:

_________________________________________________________
                        |
                                                        |
                        |       Error MONERREUR: 1 (dsBusError - bus error)
                |
                        |       with context
                                        |
                        |       value of longint is 1234567890
                        |
                        |           value of mychar is 'a'
                                |
                        |       value of lgchar is 'APPL'
                                |
                        |       __________              _________________
        _________       |
                        |       | Resume |              | ExitToShell() |
        | Debug |       |
                        |       __________              _________________
        _________       |

_________________________________________________________ .

In CHAIN '\n' or '\r' works the same.

--
Jean-Marie LABORDE          [e-mail]   or   UUCP:  imag!laborde










Path: ucivax!gateway
From: [e-mail] (Jean-Marie Laborde)
Subject: Code for Error String (2bis)
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 121
Date: 5 Apr 93 06:33:22 GMT

/*code of 3 functions, message(), FiltreDial() and extraction_texte_erreur(),
needed to build the ErrorString feature, see other e-mail */
/***************************************************************
Copyright notice
) Jean-Marie Laborde LSD2-IMAG 1992-1993
This code can be freely distributed and used, subject solely to the
following conditions
        % do not distribute changed or amended versions without prior
agreement of the author.
        % do not remove the present copyright notice
This code is probably as any piece of code not absolutely bugfree and is
not guaranteed in any manner.

This code was developed at the University of Grenoble (France) in connection
with the project Cabri-geometre.
Cabri-geometre is an integrated project for the design of ITS in the domain of
Geometry.
It is based on a microworld for Euclidian geometry called Cabri-geometre and
available from different distributors:
        in the US contact
                Brooks/Cole Pacific Grove, California 93950    1-(800) 354
9706
        outside the US contact
                Projet Cabri-geometre, LSD2-IMAG        (33) 76 51 46 16
(fax [phone])
to obtain information about local distributors and publishers in other
countries

Please send comments and/or suggestions to the following address
        Jean-Marie Laborde
        Cabri-geometre project
        LSD2-IMAG, Universit Joseph Fourier Grenoble
        Centre National de la Recherche Scientifique
        (33) 76 51 46 10    fax   [phone]
        [e-mail]


/***************************************************************

/*  % declare in your program a global myOSErr or any other suitable name  of
type OSErr;
the following #define makes the thing work */
#define MONERREUR       myOSErr

/*      %% put the following prototype where needed:
                        void    message(char *chaine,...);*/


/*  %%% make calls in your program of general type
                message("%err ResError %d ResErr=%d",MONERREUR,ResErr);

                -the simplest possible call is simply of type   message("any
C-string");

        and then        message("");

                -each time message() is called it checks if MONERREUR!=noErr
                as well as checking all the standard managers to detect any
                abnormal condition involving
                                the Resource Manager    (global ResErr
 via ResError()),
                                the System
(global DSErrCode   via SysError()),
                                the Memory Manager              (global MemErr
        via MemError()),
                                the Print Manager               (global
PrintErr        via PrError()).
                In such a case a dialog prompts with the corresponding error
string(s) in a list
                with 3 buttons:
                        % Resume                => resumes execution
                        % ExitToShell   => just exits to shell
                        % Debug                 => enters the Debugger (If the
Think C Debugger is present
we land in the code of the message() function, it is likely you will type
'command'-o)

                If no abnormal condition, message() shows the string given as
first argument CHAIN
                unless CHAIN starts with %err. In that case message() simply
returns and
                the call is absolutely transparent to the user.

                In addition, using a pattern close to formatted output, you
can output values
in the CHAIN taking advantage of the special character %:
Suppose
                        myOSErr has value 1  (Bus Error),
                        long int longint has value 1234567890,
                        char mychar has value 'a',
                        long char lgchar has value 'APPL',
then the following statement
                        message("%err with context\nvalue of longint is %ld\n    value of mychar is %c\nvalue of lgchar is %lc",longint,mychar,lgchar);
will produce following output:

_________________________________________________________
                        |
                                                        |
                        |       Error MONERREUR: 1 (dsBusError - bus error)
                |
                        |       with context
                                        |
                        |       value of longint is 1234567890
                        |
                        |           value of mychar is 'a'
                                |
                        |       value of lgchar is 'APPL'
                                |
                        |       __________              _________________
        _________       |
                        |       | Resume |              | ExitToShell() |
        | Debug |       |
                        |       __________              _________________
        _________       |

_________________________________________________________ .

In CHAIN '\n' or '\r' works the same.

--
Jean-Marie LABORDE          [e-mail]   or   UUCP:  imag!laborde










Path: ucivax!gateway
From: [e-mail] (Jean-Marie Laborde)
Subject: Code for Error String (3)
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 816
Date: 5 Apr 93 07:00:40 GMT

This is a new hopefully better sending attempt
(I am not in Grenoble but at the University of Washington (USA)
and it does nor make the things easier...)

/*code of 3 functions, message(), FiltreDial() and extraction_texte_erreur(),
needed to build the ErrorString feature, see other e-mail
          (Use 4 char tab for better reading) */
/***************************************************************
Copyright notice
Copyright Jean-Marie Laborde LSD2-IMAG 1992-1993
This code can be freely distributed and used, subject solely to the
following conditions
        o do not distribute changed or amended versions without prior
agreement of the author.
        o do not remove the present copyright notice
This code is probably as any piece of code not absolutely bugfree and is
not guaranteed in any manner.

This code was developed at the University of Grenoble (France) in connection
with the project Cabri-geometre.
Cabri-geometre is an integrated project for the design of ITS in the domain of
Geometry.
It is based on a microworld for Euclidian geometry called Cabri-geometre and
available from different distributors:
        in the US contact
                Brooks/Cole Pacific Grove, California 93950    1-(800) 354
9706
        outside the US contact
                Projet Cabri-geometre, LSD2-IMAG        (33) 76 51 46 16
(fax [phone])
to obtain information about local distributors and publishers in other
countries

Please send comments and/or suggestions to the following address
        Jean-Marie Laborde
        Cabri-geometre project
        LSD2-IMAG, Universite Joseph Fourier Grenoble
        Centre National de la Recherche Scientifique
        (33) 76 51 46 10    fax   [phone]
        [e-mail]


/***************************************************************

/*  o declare in your program a global myOSErr or any other suitable name  of
type OSErr;
the following #define makes the thing work */
#define MONERREUR       myOSErr

/*      oo put the following prototype where needed:
                        void    message(char *chaine,...);*/


/*  ooo make calls in your program of general type
                message("%err ResError %d ResErr=%d",MONERREUR,ResErr);

                -the simplest possible call is simply of type   message("any
C-string");

        and then        message("");

                -each time message() is called it checks if MONERREUR!=noErr
                as well as checking all the standard managers to detect any
                abnormal condition involving
                                the Resource Manager    (global ResErr
 via ResError()),
                                the System
(global DSErrCode   via SysError()),
                                the Memory Manager              (global MemErr
        via MemError()),
                                the Print Manager               (global
PrintErr        via PrError()).
                In such a case a dialog prompts with the corresponding error
string(s) in a list
                with 3 buttons:
                        o Resume                => resumes execution
                        o ExitToShell   => just exits to shell
                        o Debug                 => enters the Debugger (If the
Think C Debugger is present
we land in the code of the message() function, it is likely you will type
'command'-o)

                If no abnormal condition, message() shows the string given as
first argument CHAIN
                unless CHAIN starts with %err. In that case message() simply
returns and
                the call is absolutely transparent to the user.

                In addition, using a pattern close to formatted output, you
can output values
in the CHAIN taking advantage of the special character %:
Suppose
                        myOSErr has value 1  (Bus Error),
                        long int longint has value 1234567890,
                        char mychar has value 'a',
                        long char lgchar has value 'APPL',
then the following statement
                        message("%err with context\nvalue of longint is %ld\n    value of mychar is %c\nvalue of lgchar is %lc",longint,mychar,lgchar);
will produce following output:

_________________________________________________________
                        |
                                                        |
                        |       Error MONERREUR: 1 (dsBusError - bus error)
                |
                        |       with context
                                        |
                        |       value of longint is 1234567890
                        |
                        |           value of mychar is 'a'
                                |
                        |       value of lgchar is 'APPL'
                                |
                        |       __________              _________________
        _________       |
                        |       | Resume |              | ExitToShell() |
        | Debug |       |
                        |       __________              _________________
        _________       |

_________________________________________________________ .

In CHAIN '\n' or '\r' works the same.

% when if %err, %ld, %d, %f, %s, %lc or %c      has following interpretation

                                %err =>         makes the call transparent if
noErr and CHAIN starts with %err
                                %ld                     output for a long int
                                %d                      output for a int
                                %f                      output for a float
(ev. double)
                                %s                      output for a C-string
                                %lc                     output for a long to
be printed as 'APPL'
                                %c                      output for a character
                (7(BEL) => \a,  8(BS) => \b,  9(HT) => \t, 10(LF) => \n,
                 11(VT) => \v, 12(FF) => \f, 13(CR) => \r), 127 => '(dec 127)'

                characters >= 128 are printed, if possible, according the
following table

                /* not ASCII 7 bitsASCII transferable
 */


*/

/* oooo you should put the following initialisation of the system global
PrintErr=noErr;
        some where before the first call to message() or to the Print Manager
        because it seems that on most ROMs this global is initialised to -1
and not 0;
        an alternative way is to call   PrOpen();PrClose();
        after the 6 mandatory
                InitGraf(&thePort);InitWindows();InitFonts();
                InitDialogs(0L);InitCursor();TEInit();
*/

/* ooooo this code needs resource from a separate file message.rsrc
to be searched at the same level as the project or the standalone application.
If this file cannot be found message() simply returns (with a beep if an error
is present).
Note that the project must contain MacTraps and ANSI
*/


#include <MacHeaders>
#include <stdio.h>
#include <String.h>
#include <stdarg.h>

extern  OSErr   MONERREUR;

void    message         (char *chaine,...);
void    extraction_texte_erreur(OSErr monOSerreur,char *chaine,int pathRef,int
sv_pathRef);
Boolean pascal FiltreDial       (DialogPtr      Ledialogue,EventRecord
*Levent,int *Litem);
OSErr   Sonne           (char *leson);

static  Boolean erreur=FALSE;   /* permet de savoir si l'appel a sonne() vient
de message */

#define Item_duTEXTE    4



/**********************************************************************************************************************************/
void message(char *chaine, ...)
{
        int element;
        GrafPtr         sauveport;
        char            *carPtr;
        char            insertion[256+64];                      // une chaine
a inserer
        long            nbcar;
        DialogPtr       dialogue;
        int                     queltype;
        Rect            quelleboite;
        Handle          quelelement;
        int                     sauve_pathRefNum=CurResFile(),
                                pathRefNum;
        TEHandle        texte_h=0;
        Boolean         rapporte_erreur=FALSE;
        OSErr           monResErr       =ResErr,
                                monDSErrCode=DSErrCode,
                                monMemErr       =MemErr,
                                monPrintErr     =PrintErr;


// les globales d'erreur sont           ResErr,     DSErrCode,  MemErr,
 PrintErr
// les appels correspondants            ResError(), SysError(), MemError(),
PrError(),
// ATTENTION PrintErr est souvent -1 au demarrage d'une application...
// faire PrintErr=noErr dans les initialisations au debut du main

// on sauve les valeurs de ResErr, DSErrCode, monMemErr et PrintErr */

//////////////////////////////////////////////////////////////////////////////////
        if (*chaine=='%' && chaine[1]=='e' && chaine[2]=='r' && chaine[3]=='r'
                        &&
                MONERREUR==noErr && !monResErr && !monDSErrCode && !monMemErr
&& !monPrintErr)
                return;
//////////////////////////////////////////////////////////////////////////////////

        pathRefNum=OpenResFile("\pmessage.rsrc");
        if (ResErr || pathRefNum==-1){          // en absence de message.rsrc
!!!!!
                if (MONERREUR || monResErr || monDSErrCode || monMemErr ||
monPrintErr)
                        SysBeep(1);
                //Debugger();
                ResErr=0;  // in case of a subsequent call to message()
                return;
        }
        UseResFile(pathRefNum);         // juste pour le cas ou message.rsrc
serait deja ouvert
        if (ResErr){
                CloseResFile(pathRefNum);
                SysBeep(1);
                return;
        }

        dialogue=GetNewDialog(128,NULL,(WindowPtr) -1);
        UseResFile(sauve_pathRefNum);
        if (!dialogue) {
                CloseResFile(pathRefNum);
                SysBeep(1);
                return;
        }
        GetPort(&sauveport);
        SetPort(dialogue);

        SetCursor(&arrow);
        GetDItem(dialogue,Item_duTEXTE,&queltype,&quelelement,&quelleboite);
        texte_h=TENew(&quelleboite,&quelleboite);
//(*texte_h)->txFont=times;

        if (carPtr=strchr(chaine,'%')){
/* la chaine necessite un traitement special, sinon trivial */
/* on fait une analyse de la chaine  T_C UserManual p 268 */
/* on devrait verifier le nbre de param == #car % !!! */
                        va_list suite_des_args;
                        long    longarg;
                        char    *chainearg, chararg;
                        int             intarg;
                        float   floatarg;
                        double  doublearg;
                        char    *sv_carPtr=&chaine[0],
                                        chaine_aux[256];        /* 256
intervient aussi dans extraction_texte_erreur */

                        erreur=FALSE;
                        va_start(suite_des_args,chaine);
/* chaine est le dernier argument nomme */
                        while (carPtr=strchr(carPtr,'%')){
                                char    *insertPtr;
                                int             nbcar;

/* remplacement des \n par des \r */
                                strncpy((char
*)insertion,sv_carPtr,carPtr-sv_carPtr);
                                for (nbcar=0;nbcar<carPtr-sv_carPtr;nbcar++)
                                        if (insertion[nbcar]=='\n')
insertion[nbcar]='\r';

                                TEInsert((char
*)insertion,carPtr-sv_carPtr,texte_h);

                                carPtr++;
/*****************/
                                if (*carPtr=='e' && *(carPtr+1)=='r' &&
*(carPtr+2)=='r'){
                                        carPtr+=3;
// on ecrit le nom des variables d'erreur MONERREUR, ResErr, DSErrCode,
MemErr, PrintErr
// suivi du code et da signification
rap_erreur:
                                        if (MONERREUR){
                                                insertPtr=&insertion[0];
                                                strcpy(insertPtr,"\rError
MONERREUR: ");
                                                insertPtr=strchr(insertPtr,0);


NumToString(MONERREUR,chaine_aux);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr++='
';*insertPtr++='('; /*)*/


extraction_texte_erreur(MONERREUR,chaine_aux,pathRefNum ,sauve_pathRefNum);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr=0;


TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                                /*(*/
TEInsert(")",1L,texte_h);
                                                erreur=TRUE;
                                        }
                                        if (monResErr){
                                                insertPtr=&insertion[0];
                                                strcpy(insertPtr,"\rErreur
ResourceMgr ResErr: ");
                                                insertPtr=strchr(insertPtr,0);


NumToString(monResErr,chaine_aux);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr++='
';*insertPtr++='('; /*)*/


extraction_texte_erreur(monResErr,chaine_aux,pathRefNum ,sauve_pathRefNum);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr=0;


TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                                /*(*/
TEInsert(")",1L,texte_h);
                                                erreur=TRUE;
                                        }
                                        if (monDSErrCode){
                                                insertPtr=&insertion[0];
                                                strcpy(insertPtr,"\rErreur
Systeme DSErrCode: ");
                                                insertPtr=strchr(insertPtr,0);


NumToString(monDSErrCode,chaine_aux);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr++='
';*insertPtr++='('; /*)*/


extraction_texte_erreur(monDSErrCode,chaine_aux,pathRefNum ,sauve_pathRefNum);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr=0;


TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                                /*(*/
TEInsert(")",1L,texte_h);
                                                erreur=TRUE;
                                        }
                                        if (monMemErr){
                                                insertPtr=&insertion[0];
                                                strcpy(insertPtr,"\rErreur
MemoryMgr MemErr: ");
                                                insertPtr=strchr(insertPtr,0);


NumToString(monMemErr,chaine_aux);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr++='
';*insertPtr++='('; /*)*/


extraction_texte_erreur(monMemErr,chaine_aux,pathRefNum ,sauve_pathRefNum);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr=0;


TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                                /*(*/
TEInsert(")",1L,texte_h);
                                                erreur=TRUE;
                                        }
                                        if (monPrintErr){
                                                insertPtr=&insertion[0];
                                                strcpy(insertPtr,"\rErreur
PrintMgr PrintErr: ");
                                                insertPtr=strchr(insertPtr,0);


NumToString(monPrintErr,chaine_aux);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr++='
';*insertPtr++='('; /*)*/


extraction_texte_erreur(monPrintErr,chaine_aux,pathRefNum ,sauve_pathRefNum);

strncpy(insertPtr,chaine_aux+1,chaine_aux[0]);
                                                insertPtr+=chaine_aux[0];
                                                *insertPtr=0;


TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                                /*(*/
TEInsert(")",1L,texte_h);
                                                erreur=TRUE;
                                        }
                                        if (!erreur){
                                                strcpy((char
*)insertion,"\r(Apparemment pas d'erreur systeme)\r");
                                                insertPtr=strchr((char
*)insertion,0);

TEInsert(insertion,insertPtr-&insertion[0],texte_h);
                                        }
                                        else{
                                                TEInsert("\r",1L,texte_h);
                                        }
/* on mange en cas de milieu le premier blanc de la suite de la chaine */
                                        if (!rapporte_erreur){
                                                if (*carPtr==' ') carPtr++;
                                        }
                                        sv_carPtr=carPtr;
                                        if (rapporte_erreur) goto
fin_rap_erreur;
                                        continue;
                                }
                                else if (*carPtr=='s'){
                                        chainearg=va_arg(suite_des_args,char
*);
                                        nbcar=strlen(chainearg);
                                        if (nbcar>255) chainearg[255]=0;
                                        strcpy((char *)insertion,chainearg);
/* mise de insertion entre " et " */
                                        CtoPstr((char *)insertion);
                                        nbcar=insertion[0]+1;
                                        insertion[0]='\"';
                                        if (nbcar<255-1){
                                                insertion[nbcar++]='\"';
                                                insertion[nbcar]=0;
                                        }
                                        else{
                                                insertion[254]='\"';
                                                insertion[255]=0;
                                        }
                                }
                                else if (*carPtr=='l' && *(carPtr+1)=='d'){
                                        longarg=va_arg(suite_des_args,long);
                                        carPtr++;
                                        NumToString(longarg,insertion);
                                        PtoCstr(insertion);
                                }
                                /*else if (*carPtr=='d' &&
*(carPtr+1)=='f'){*/
/*
doublearg=va_arg(suite_des_args,double);*/
/*                                      carPtr++;*/
/*                                      sprintf((char *)insertion,"%g",
doublearg);*/
/*                              }*/
                                else if (*carPtr=='d'){
                                        intarg=va_arg(suite_des_args,int);
                                        NumToString((long)intarg,insertion);
                                        PtoCstr(insertion);
                                }
                                else if (*carPtr=='f'){

//floatarg=va_arg(suite_des_args,float);        // ne marche pas

//floatarg=va_arg(suite_des_args,double);

doublearg=va_arg(suite_des_args,double);
                                        sprintf((char *)insertion,"%g",
doublearg); // precision par defaut 6
                                }
                                else if (*carPtr=='l' && *(carPtr+1)=='c'){
                                        unsigned char c, nombre[4];
#include <ctype.h>
#define AFFICHE(car)    if (isprint(c) || (127<c && c<255))                { nombre[0]=c;nombre[1]=0;strcat((char *)insertion,(char
*)nombre);}                                                else{        switch(car){                case 0: strcat((char *)insertion,"\\0");break;                case 1: strcat((char *)insertion,"\\1");break;                case 2: strcat((char *)insertion,"\\2");break;                case 3: strcat((char *)insertion,"\\3");break;                case 4: strcat((char *)insertion,"\\4");break;                case 5: strcat((char *)insertion,"\\5");break;                case 6: strcat((char *)insertion,"\\6");break;                case 7: strcat((char *)insertion,"\\a");break;                case 8: strcat((char *)insertion,"\\b");break;                case 9: strcat((char *)insertion,"\\t");break;                case 10: strcat((char *)insertion,"\\n");break;                case 11: strcat((char *)insertion,"\\v");break;                case 12: strcat((char *)insertion,"\\f");break;                case 13: strcat((char *)insertion,"\\r");break;                default:                        NumToString((long)c

a
                        strcat((char *)insertion,"(dec ");                        strcat((char *)insertion,(char *)nombre);                        strcat((char *)insertion,")");break;}}

                                        longarg=va_arg(suite_des_args, long);
                                        carPtr++;
                                        insertion[0]=0;

                                        if (longarg/256==0){
/* en fait probablement un simple caractere */
                                                c=longarg;
                                                AFFICHE(c);
                                        }
                                        else{
                                                c=longarg>>24;
                                                AFFICHE(c);
                                                longarg<<=8;

                                                c=longarg>>24;
                                                AFFICHE(c);
                                                longarg<<=8;

                                                c=longarg>>24;
                                                AFFICHE(c);
                                                longarg<<=8;

                                                c=longarg>>24;
                                                AFFICHE(c);
                                        }
/* mise de insertion entre ' et ' */
                                        CtoPstr((char *)insertion);
                                        nbcar=insertion[0]+1;
                                        insertion[0]='\'';
                                        insertion[nbcar++]='\'';
                                        insertion[nbcar]=0;
                                }
                                else if (*carPtr=='c'){
                                        unsigned char c, nombre[4];
                                        c=va_arg(suite_des_args, int);
                                        insertion[0]=0;

                                        AFFICHE(c);
/* mise de insertion entre ' et ' */
                                        CtoPstr((char *)insertion);
                                        nbcar=insertion[0]+1;
                                        insertion[0]='\'';
                                        insertion[nbcar++]='\'';
                                        insertion[nbcar]=0;
                                }
                                else{
/******************/
// % suivi de Type inconnu
                                        insertion[0]=' ';insertion[1]=0;
                                }
                                TEInsert(insertion,strlen(insertion),texte_h);
                                sv_carPtr=++carPtr;
                        }
                        va_end(suite_des_args);
/* on insere la fin de la chaine avec echange de \n */
                        carPtr=strchr(sv_carPtr,0);
                        strncpy((char *)insertion,sv_carPtr,carPtr-sv_carPtr);
                        for (nbcar=0;nbcar<carPtr-sv_carPtr;nbcar++)
                                if (insertion[nbcar]=='\n')
insertion[nbcar]='\r';

                        TEInsert((char *)insertion,carPtr-sv_carPtr,texte_h);
                }
                else{
                        strcpy((char *)insertion,chaine);
                        carPtr=&insertion[0];
                        while(*carPtr++)
                                if (*carPtr=='\n') *carPtr='\r';
                        TESetText((char
*)insertion,strlen(insertion),texte_h);
                }

/* pour  rapporter une erreursysteme meme sinon explicitement demande */
fin_rap_erreur:
        if (!rapporte_erreur && !erreur) {                      // ie au
premier passage
                if (MONERREUR || monResErr || monDSErrCode || monMemErr ||
monPrintErr){
                        rapporte_erreur=TRUE;
                        TEInsert("\r",1L,texte_h);
                        goto rap_erreur;
                }
        }

        {
                int nbreLignes;
/* on compte le nombre de lignes */
                TECalText(texte_h);
                nbreLignes=(*texte_h)->nLines;


                if (nbreLignes>1){
                        int
hauteur=((WindowPtr)dialogue)->portRect.bottom-((WindowPtr)dialogue)->portRect.top,

largeur=((WindowPtr)dialogue)->portRect.right-((WindowPtr)dialogue)->portRect.left,
                                offset=(nbreLignes-1)*(*texte_h)->lineHeight;

                        SizeWindow(dialogue,largeur,hauteur+offset,FALSE);

/* on pourrait mettre un boucle de 1 a  (Item_duTEXTE-1) */


GetDItem(dialogue,OK,&queltype,&quelelement,&quelleboite);
                        OffsetRect(&quelleboite,0,offset);

SetDItem(dialogue,OK,queltype,quelelement,&quelleboite);
                        MoveControl(quelelement,quelleboite.left,
quelleboite.top);


GetDItem(dialogue,Cancel,&queltype,&quelelement,&quelleboite);
                        OffsetRect(&quelleboite,0,offset);

SetDItem(dialogue,Cancel,queltype,quelelement,&quelleboite);
                        MoveControl(quelelement,quelleboite.left,
quelleboite.top);


GetDItem(dialogue,Cancel+1,&queltype,&quelelement,&quelleboite);
                        OffsetRect(&quelleboite,0,offset);

SetDItem(dialogue,Cancel+1,queltype,quelelement,&quelleboite);
                        MoveControl(quelelement,quelleboite.left,
quelleboite.top);

                        (*texte_h)->destRect.bottom+=offset;
                        (*texte_h)->viewRect.bottom+=offset;
                }
//On centre le dialogue;
                {
                        int decal_h,decal_v;
                        Rect r;
                        r=screenBits.bounds;
                        decal_h=((r.right-r.left)
                                                -

(dialogue->portRect.right-dialogue->portRect.left))/2
                                                        -

dialogue->portRect.left;

                        decal_v=(342            /* centrage vert. comme sur un
ecran de 9 pouces */
                                                -

(dialogue->portRect.bottom-dialogue->portRect.top))/2
                                                -
                                                dialogue->portRect.top;

                        MoveWindow(dialogue,decal_h,decal_v,FALSE);
                }
        }
        {
                ProcPtr sauveMenuHook=MenuHook,
                                sauveMBarHook=MBarHook;

                MenuHook= NULL;
                MBarHook= NULL;

                ShowWindow(dialogue);
                PenSize(3,3);
                {
                        int no_item=OK;
                        if (erreur) no_item=Cancel;

GetDItem(dialogue,no_item,&queltype,&quelelement,&quelleboite);
                }
                InsetRect(&quelleboite,-4,-4);
                FrameRoundRect(&quelleboite,16,16);PenNormal();

                TEUpdate(&(*texte_h)->viewRect,texte_h);
                DrawDialog(dialogue);
                do {
                        ModalDialog(FiltreDial,&element);
                }
                while (element!=OK && element!=Cancel && element!=(Cancel+1));
                SetPort(sauveport);
                DisposDialog(dialogue);

                MenuHook= sauveMenuHook;
                MBarHook= sauveMBarHook;

                TEDispose(texte_h);
                UseResFile(sauve_pathRefNum);
                CloseResFile(pathRefNum);
                erreur=FALSE;

                if (element==Cancel) ExitToShell();
                if (element==Cancel+1) Debugger();
// dans le debugger de ThinkC faire maintenant "out" ...
        }
}

/******************************************************************/
Boolean pascal FiltreDial(DialogPtr Ledialogue,
                                                EventRecord *Levent,
                                                int             *Litem)
{
        char car;
        int type;
        Handle hit;
        Rect itr;

        if( (Levent->what==keyDown)){
                car=Levent->message%256;
                if (car=='\r' || car==3)
                {
                        long finalTicks;
                        int     no_item=OK;
                        if (erreur) no_item=Cancel;

                        GetDItem(Ledialogue,no_item,&type,&hit,&itr);
                        HiliteControl(hit,1);
                        Delay(10L,&finalTicks);
                        *Litem=no_item;
                        return TRUE;
                }
        }
        return FALSE;
}


/* on introduit le message d'erreur eventuel */
/*************************************************************************************/
void extraction_texte_erreur(OSErr monOSerreur,char *chaine,int pathRef,int
sv_pathRef)
/* renvoie une chaine Pascal dans chaine */
{
        Handle erreur_texte=0L;
        char    code_litteral[16];
        int             nbcar;
        long    taille;
        OSErr   sv_MemErr=MemErr,  // pour ne pas poluer MemErr
                        sv_ResErr=ResErr;

        char *textePtr, *carPtr, *finPtr;
        NumToString((long)monOSerreur,code_litteral);
        nbcar=code_litteral[0];
        code_litteral[0]='\r';
        code_litteral[nbcar+1]=' ';
        code_litteral[nbcar+2]=0;
/* on a entoure le nombre devenu chaine C (code_litteral) d'un RC et d'un ' '
*/

        UseResFile(pathRef);
        erreur_texte=GetResource('TEXT',128);
        UseResFile(sv_pathRef);
        if (ResErr) {
                ResErr=sv_ResErr;
                strcpy((char *)chaine,"(ressource 'TEXT' id=128 non
disponible)");
                PtoCstr((char *)chaine);
                return;
        }

        {
                taille=GetHandleSize(erreur_texte);
                SetHandleSize(erreur_texte,taille+2L);
                if (MemErr){
                        MemErr=sv_MemErr;
                        *(*erreur_texte+taille-1)=0;
                }
                else{
                        *(*erreur_texte+taille)='\r';
                        *(*erreur_texte+taille+1)=0;
                }
                HLock(erreur_texte);
                textePtr=*erreur_texte;
                carPtr=strstr(textePtr,(char *)code_litteral);
                if (carPtr){
/* on avance sur les caracteres du code litteral */
                        carPtr+=nbcar+2;
                        while(*carPtr++==' ');
                        carPtr--;
                        finPtr=strchr(carPtr,'\r');
                        if (finPtr){
                                *finPtr=0;
                                nbcar=finPtr-carPtr;
                                nbcar=(nbcar<255)?nbcar:255;
                                strncpy((char *)chaine,carPtr,nbcar+1);
                                *finPtr='\r';
                        }
                        else{  /* on a le dernier (obsolette depuis qu'on a
rajoute un '\r' et un 0) */
                                nbcar=strlen(carPtr);
                                nbcar=(nbcar<255)?nbcar:255;
                                strncpy((char *)chaine,carPtr,nbcar+1);
                                chaine[nbcar]=0;
                        }
                }
                else{
/* erreur non-referencee */
                        strcpy((char *)chaine,"not a referenced error!");
                }
                HUnlock(erreur_texte);
        }
        CtoPstr(chaine);
}
/**********************************************************************************************************************************/

--
Jean-Marie LABORDE          [e-mail]   or   UUCP:  imag!laborde










Path: ucivax!gateway
From: [e-mail] (PJ Vandal)
Subject: request Info about think class library
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 26
Date: 5 Apr 93 08:22:44 GMT

I'm looking for a resource. I want to learn how to use the Think class
library with Think C.

I have verison 4.0. I've done some C programming in various environments,
including conventional (not object) on the mac. I have the Dave Mark books on
programming in C on the mac, and I've read the manual that comes with Think C
4.0 several times. I've had several university (upper division) programming
classes in C and Pascal, and I understand the concept of object oriented
programming, but have very little actual experience doing oop.

I know a little bit about programming the mac, enough to cobble together
fairly simple applications. What I'd really like to find is information on
using the TCL that doesn't assume that I already know a lot about C++. I
guess I could read a book on C++, but if there were something out there that
would teach me what a general book on C++ would, but in the context of using
the Think class library instead, that would be really good.

I'm not a professional programmer, and won't do *that* much development. Is
it really worthwhile to get the 5.0 upgrade? Is there anything I should know
about using 4.0 if I don't?

Also, one of the main things that I'm interested in is user interface design,
particularly writing custom user interface elements (like custom windows and
buttons), so any information on learning about these things would be helpful
too.











Path: ucivax!gateway
From: [e-mail] (Dave Nebinger)
Subject: ?? TESetText Fails ??
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 43
Date: 6 Apr 93 20:33:40 GMT
References: <[e-mail]> <[e-mail]>

  I have an appl that reads in a resource and uses the text in that
resource in a TE record.  Before the call to TESetText the handles are
locked down, and they are valid handles.  Using TC's debugger I have
looked at the data in the handle as well as the data in the TEHandle.

  In the following code, TESetText fails:

TextStyle style;
void * ptr;

style.tsFont=geneva;
style.tsSize=12;
style.tsFace=0;

HLock(gResOther);
HLock(TE_otherText);

i=GetHandleSize(gResOther);

TESetText(*gResOther,i,TE_otherText);

/*
  In the TE record, teLength & everything else is updated to show
  that some setting had occured.  But *(**TE_otherText).hText is a
  null string.
*/

TESetSelect(0,32767,TE_otherText);

TESetStyle(doFont+doSize+doFace,&style,TRUE,TE_otherText);

TEActivate(TE_otherText);

HUnlock(TE_otherText);
HUnlock(gResOther);



  Why would TESetText fail?  I check TR 2.0, but it does not say that
TESetText could fail (or at least not do what it should)...  Any
assistance would be greatly appreciated.

[e-mail]










Path: ucivax!gateway
From: [e-mail] (Rich Siegel)
Subject: Re:  ?? TESetText Fails ??
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 4
Date: 6 Apr 93 22:35:56 GMT

Don't lock the TEHandle; it's a variable-size data structure that needs to
grow. Locking the handle to your text -is- the correct thing to do, however.

R.










Path: ucivax!gateway
From: [e-mail] ("The sky is ecstasy dancing...")
Subject: The Time Manager
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 32
Date: 8 Apr 93 19:44:48 GMT
X-Vmsmail-To: SMTP%"[e-mail]"

I have been playing with the Time Manager, trying to discover how to use it.
One thing that I noticed, is that if you ever want to do a multiplication or
division of long ints, you must have the A5 register set to your application
A5.  If not, you will go into never never land.  Example, you set up your
routine to go off at a given time X.  When the routine is supposed to go off,
the OS apperently interupts the current process, and does the routine.  Since
it was an interupt the machine is currently using the OS A5.  When you try to
do a system call, the system does not return to the correct place, and dies.

After fighting with this (God I love MacsBug, it made solving this problem
feasable), I have come to the assumption, that the reason that this is
happening is that the long mult/division, are implemented as a subroutine of
the Mac OS.  Because of this, it apperently trys to jump back to the routine
that called it, instead of returning.  Since the A5 is pointing to the OS
globals instead of the application globals, it goes to the wrong place.  Can
anyone confirm or deny this?  I am going on conjecture, cause IM does not tell
me how the Time Manager works, it just tells me, sort of, how to use it.

Another problem that is occuring, is that I try to do a Get1Resource (or
something similar, I am trying to get a resource from the applications resource
file, not every open resource file around), and I don't get the resource that I
want.  If the above is correct, am I trying to get my resource from the OS
resource file, even thought the current application is mine?

Thanks,
   Mike

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[e-mail]        Loose cannon and programmer of Vaxes
[e-mail]    I don't work for anybody, so I don't
[e-mail]        need a disclaimer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










Path: ucivax!gateway
From: [e-mail] (Pete Resnick)
Subject: Re: The Time Manager
X-Sender: [e-mail]
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 43
Date: 9 Apr 93 08:57:21 GMT

At  7:44 PM 4/8/93 +0000, The sky is ecstasy dancing... wrote:

>One thing that I noticed, is that if you ever want to do a multiplication or
>division of long ints, you must have the A5 register set to your application
>A5.
>
>I have come to the assumption, that the reason that this is
>happening is that the long mult/division, are implemented as a subroutine of
>the Mac OS.

You were close, but you made the wrong diagnosis. It is true that the
touble you are having is in part due to A5 being wrong, but it is much
worse than you think. The long mult/div are not Mac OS, but THINK C glue
that is added to your program. The problem is that this glue obviously
ended up in a different segment from the one containing the Time Manager
task. In the best case, the long mult/div glue will be in a segment that is
loaded and locked at the time you need to call it; in that case, all you
need to do is set up A5, for which there are instructions in IM VI. In the
worst case, if the segment with the glue is not loaded, any attempt to load
the segment will crash the machine since you cannot call anything that will
cause the Memory Manager to kick in at interrupt time, and the Segment
Loader is a pretty bad offender. You cannot allocate or move memory at
interrupt, and the Segment Loader is sure to do that.

>Another problem that is occuring, is that I try to do a Get1Resource...

If you are trying to do this in the Time Manager task, it will most
certainly fail. Calling Get1Resource allocates memory for the resource and
hence cannot be called from interrupt.

Programming at interrupt is very limiting and is not for the faint of
heart. My recommendation is to have your Time Manager task set up A5, set a
global flag, and have your main event loop do what needs to be done. If you
have something that really needs to be done in a time sensitive way,
allocate and lock all memory before it will need to be called.

pr
--
Pete Resnick        (...so what is a mojo, and why would one be rising?)
Graduate assistant - Philosophy Department, Gregory Hall, UIUC
System manager - Cognitive Science Group, Beckman Institute, UIUC
Internet: [e-mail]











Path: ucivax!gateway
From: [e-mail] (Francois Menneteau)
Subject: Re: The Time Manager
Message-ID: <[e-mail]>
In-Reply-To: "The sky is ecstasy dancing..."'s message as of Apr  8, 19:44.
Newsgroups: fa.think-c
Organization: IMAG Institute, University of Grenoble, France
Lines: 18
Date: 9 Apr 93 10:14:08 GMT

[8 Apr]. In your message you write:
>After fighting with this (God I love MacsBug, it made solving this problem
>feasable), I have come to the assumption, that the reason that this is
>happening is that the long mult/division, are implemented as a subroutine of
>the Mac OS.  Because of this, it apperently trys to jump back to the routine

Yes you are right. The 68000 is not able to do 32 bits multiplication (only
16 bits x 16 bits with the result put in 16 or 32 bits is possible).

I can't remember if 68020 and higher family can, but I suppose either you
have a 68000 based machine, or the compiler does not use them (either because
you do not tell it [i.e. generate 68020 code] or because it can't).

--
Francois Menneteau ()   __|||||__   () "... I had their lives in my hands
================== ()    /O   O\    () their fate their fortune in my visions
[e-mail]       ()    - .|. -    () No one believed in my true prophecy
================== ()     \=^=/     () And now it's too late."  (Iron Maiden)










Path: ucivax!gateway
From: [e-mail] (Christopher Evans)
Subject: Discipline
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 16
Date: 13 Apr 93 13:29:13 GMT


    What is wrong with Discipline?  I get a buss error whenever I
try to install it as an init in my System Folder.  Is there a problem
with System 7.1?

<==================================Q======================================>
  Chris Evans                      |   Internet: [e-mail]
  Development                      |   Phone: [phone]
  Natural Intelligence, Inc.       |   FAX:   [phone]
  2067 Massachusetts Avenue        |   AppleLink: NATURAL
  Cambridge MA  02140              |   or [e-mail]@INTERNET#

 Vital papers will demonstrate their vitality by spontaneously moving
    from where you left them to where you can't find them.












Path: ucivax!gateway
From: [e-mail] (Aaron Barnett)
Subject: JADG
Message-ID: <[e-mail]>
Content-transfer-encoding: 7BIT
MIME-version: 1.0
Newsgroups: fa.think-c
X-VMS-To: TOE::IN%"[e-mail]"
Lines: 1
Date: 13 Apr 93 17:55:29 GMT
X-Envelope-to: [e-mail]

where can I find JADG (afterdark glue)?










Path: ucivax!gateway
From: [e-mail] ("The sky is ecstasy dancing...")
Subject: Time Manager Summary
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 36
Date: 13 Apr 93 20:25:03 GMT
X-Vmsmail-To: SMTP%"[e-mail]"

I recently was playing with the Time Manager, and ran into a few problems.  I
documented them in an earlier message, but to sum up, when my routine was
activated at interupt time, some things would work sometimes, others would not
do anything, and still others would crash the computer.  Here is the answers I
recieved:

   Doing anything important during at interupt time is generally dangerous.  It
was suggested (1) that I set a flag, and have the main program notice that the
flag was set, and then do what I needed to do.

   My specific problem was that I was doing mult/div of long ints.  Think C
adds a special glue to do the mult/div.  This means that the segement with this
glue may or may not be loaded at the time it is needed.  Since you can do
anything that needs the Memory Manager at interrupt time, loading that segement
will cause problems.

   The above was also the problem with the Get1Resource call.  This calls the
Memory Manager as well, in order to allocate memory.

   One last suggestion, was to make sure that the compiler compiled with 68020
code instead of 68000.  I haven't had time to try this yet, but it could help
in getting rid of that special glue. :)

Thanks to:

 Pete Resnick
 Jens-Uwe Mager
 Francois Mennetau

Mike

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[e-mail]        Loose cannon and programmer of Vaxes
[e-mail]    I don't work for anybody, so I don't
[e-mail]        need a disclaimer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










Path: ucivax!gateway
From: [e-mail] ("Zack T. Smith")
Subject: After Dark
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 8
Date: 13 Apr 93 21:25:06 GMT


Has anyone got a description of how to code for After Dark that they could
send me?

Thanks in advance

Zack











Path: ucivax!gateway
From: [e-mail] (WES COVALT)
Subject: list clikLoop
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 10
Date: 13 Apr 93 22:48:25 GMT

I need to tweak the list manager's clikLoop routine and I've
stumbled upon an interesting anomaly.  I am supposed to be
able to get the mouse location in the list from
(*myList)->mouseLoc, but I get wierd results.  For example, if
the local point is 4,4, I might get 140,20.

I'm so puzzled I don't even know what other information to give.
If anyone has worked on a list clikLoop, I'd appreciate some
suggestions.
                                   Wes










Path: ucivax!gateway
From: [e-mail]
Subject: problem with sprintf?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 15
Date: 14 Apr 93 04:45:11 GMT

I'm using Think C 5.04.  Is there a known problem with
printing floats and long doubles or am I just being stupid?

#include <stdio.h>
char aString[256];
long double aNumber;

sprintf(aString,"%Lg",aNumber);

doesn't work at all (neither do %Le or %Lf, nor does %f with a float)
for me.

Thanks,
Ian Dowell
[e-mail]










Path: ucivax!gateway
From: [e-mail] (Jim Lynch)
Subject: Re:  Time Manager Summary
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 10
Date: 14 Apr 93 13:19:26 GMT

I just _have_ to clean up one tiny detail:

Mike sed:
>>>>>
Since you can do
anything that needs the Memory Manager at interrupt time,
<<<<<

Must be a typo. should read: Since you can't do anything that needs the
Memory Manager at interrupt time,










Path: ucivax!gateway
From: [e-mail] ("The sky is ecstasy dancing...")
Subject: Mistake
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 14
Date: 14 Apr 93 15:50:15 GMT
X-Vmsmail-To: SMTP%"[e-mail]"

Argh.

Thanks to Jim Lynch for catching my typo.  Yes that should have said:

"Should NOT" use memory management anything at interupt time.  Sorry about that
folks. :(

Mike

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[e-mail]        Loose cannon and programmer of Vaxes
[e-mail]    I don't work for anybody, so I don't
[e-mail]        need a disclaimer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










Path: ucivax!gateway
From: [e-mail] (Paul Franklin)
Subject: Re: Time Manager Summary
Message-ID: <[e-mail]>
In-Reply-To: Your message of "13 Apr 93 20:25:03 PST."
             <[e-mail]>
Newsgroups: fa.think-c
Reply-To: [e-mail]
Lines: 15
Date: 14 Apr 93 23:13:29 GMT


Mike's message dated: 13 Apr 93 20:25:03 PST
>
>   My specific problem was that I was doing mult/div of long ints.
>Think C adds a special glue to do the mult/div.  This means that the
>segement with this glue may or may not be loaded at the time it is
>needed.  Since you can do anything that needs the Memory Manager at
>interrupt time, loading that segement will cause problems.

One way to solve this is to do a mult/div of long ints during
initialization, causing the glue to be loaded before the Time Manager
is ever called; thus, the glue is loaded at non-interrupt time but
used at interrupt time.

--Paul Franklin










Path: ucivax!gateway
From: [e-mail] ("Robert M. Fuhrer")
Subject: Use Think C 5 to make MPW tools?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Reply-To: [e-mail]
Lines: 11
Date: 15 Apr 93 00:11:17 GMT

Anyone know whether this is possible? Direct e-mail answers, please; I haven't
yet subscribed to the mailing list.

--------------------------
Robert M. Fuhrer
Computer Science Department
Columbia University
503 CSC Building
[phone]

Internet: [e-mail]










Path: ucivax!gateway
From: [e-mail] (Ray Ingles)
Subject: Why would a program run in the Debugger and not normally?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 17
Date: 15 Apr 93 07:41:12 GMT


 I'm using Think C 5.0.4 on a Mac Classic II (System 7, obviously). I have
all the optimizations off, and the "Think C + Objects" on. When I run my
program using the debugger, it works just fine. If I try to run it without
the debugger, or without a breakpoint set at one particular function, I
get a crash - it just exits.
 Note, I don't actually *do* anything at this breakpoint. I just go, then
it stops at the breakpoint, then I go again. If the breakpoint is off, I get
a 'bus error'.
 Now, obviously the debugger changes how the program is run. But does what
I'm describing offer any hint as to *what* is wrong?

 Sincerely,

 Raymond Ingles                       [e-mail]

 "An apple every eight hours keeps three doctors away." - B. Kliban










Path: ucivax!gateway
From: [e-mail]
Subject: Get info
Message-ID: <9304150846.AA08580@igg_amethyst.igg.tno.nl>
Content-transfer-encoding: 7BIT
Newsgroups: fa.think-c
Lines: 2
X-Mts: smtp
Date: 15 Apr 93 09:47:55 GMT
X-Envelope-to: [e-mail]

help
dir










Path: ucivax!gateway
From: [e-mail] (Jeremy John Ahouse)
Subject: Re: Why would a program run in the Debugger and not normally?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 18
Date: 15 Apr 93 15:09:50 GMT

Raymond,
> Now, obviously the debugger changes how the program is run. But does what
>I'm describing offer any hint as to *what* is wrong?

        I don't know exactly what is happening with your program, but
frequently this kind of thing come from passing a pointer to a structure
that has not been defined in the current scope.  So there may be memory
available for it when you are running the debugger and you walk off into
disaster when the debugger is not on.  C doesn't check to see if the memory
that is pointed to is really reserved and full of what you claim it is
(e.g. a pointer to a Rect).

        So be sure that you are defining the datastructures in a local
scope (i.e. within the function) before you pass the addresses to functions
that will operate on that memory (eg SetRect).

        - Jeremy











Path: ucivax!gateway
From: [e-mail] (Ray Ingles)
Subject: Okay, *that's* why.
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 38
Date: 15 Apr 93 20:44:29 GMT


 I have received a bunch of responses to my question about why a program
would run in the debugger and not directly. Thanks to:

 Lawrence K. Cormack
 Cheinan Marks
 J. Michael Morrison
 Gary Leydon
 Edward J. Huff
 TAIHOU

 I also received a couple requests to summarize responses. Possible causes
of problems like this include:

 1) Using pointers, handles, or arrays in bad ways. Trashing memory when
    you're in the debugger is not always fatal; it can just trash the
    debugger's memory and still limp through to the end. (This, by the way,
    was my problem. One *little* string, not allocated properly...)

 2) Failing to initialize the various managers and such. The debugger will
    often do this for you, so your program will run fine when in the debugger
    but not when you run it alone.

 3) You may have found a bug in the Mac OS or the debugger. Don't bet on it.

 (Note, Cheinan Marks suggested using SysBeep() calls to find out if code
was being executed rather than setting breakpoints. This way, you can find
out if it's your code, or a problem with how it interacts with the debugger.)

 Thanks again for the help! We're back on track, which is a good thing since
it's due Tuesday! :->

 Sincerely,

 Ray Ingles               [e-mail]

 "Icky icky icky icky fKANG zoop-boing n zowzyin..." -The Knights Who
So Recently Said "NEE!"










Path: ucivax!gateway
From: [e-mail] ("The sky is ecstasy dancing...")
Subject: garbaled return address.
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 13
Date: 15 Apr 93 21:00:33 GMT
X-Vmsmail-To: SMTP%"[e-mail]"

Sorry to waste the bandwidth, but someone out there sent me a message, and
their return address was trashed, so I am sending to the regular list.

From what I could get, it was J. Wachs from JPMORGAN.COM.  Unfortunately,
everything I tried to send you bounced.  Please give me a return address.

Mike

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[e-mail]        Loose cannon and programmer of Vaxes
[e-mail]    I don't work for anybody, so I don't
[e-mail]        need a disclaimer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










Path: ucivax!gateway
From: [e-mail]
Subject: sprintf answers
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 82
Date: 15 Apr 93 22:54:40 GMT

Thanks to all who replied.  It turned out the problem was
that ANSI had been compiled with Universal floating point
and my project had been compiled with Native floating point.

Here are the answers I got...

----------------------------------------------------
From: "Howard Rafal" <[e-mail]>
It sounds like a pointer problem to me.  Think C is kind of flaky with
strings of the form [].  Just to be sure, I would try:

    (char *)&astring[0];

-----------------------------------------------------
From: [e-mail]

I think the problem is in the language settings of your compiler. When you
use routines from <stdio.h> they assume a general floating point point
format. There is a section about this in the user's manual.
Hope this helps.


--------------------------------------------------------------------------
From: [e-mail] (B. Kirsch)

Shouldn't you be using lower case L as:
sprintf(aString,"%lfg",aNumber);
?

Barry Kirsch
[e-mail]

***** the manual says "L" but "l" probably works too

-----------------------------------------------------
From: [e-mail] (B. Kirsch)

sprintf(aString,"%lf",aNumber);
-----------------------------------------------------
From: "Kirk Crawford" <[e-mail]>

#include <stdio.h>
Str255  aString;            /* Str255's are more common in Mac programs */

double aNumber;             /* you don't need the 'Long' type */

sprintf(aString,"%lg",aNumber);  /* the l should be lower case */
sprintf(aString,"%lf",aNumber);
sprintf(aString,"%le",aNumber);

-----------------------------------------------------
From: Jim Van Peursem <[e-mail]>

  Neither. Are you using ANSI-small? Open up this ANSI-small project
and look at the printf code. They #ifdef out the floating point
printing stuff. I made a copy of this project and #ifdef'd it back
in. Works great now!

-----------------------------------------------------
From: "Bin Zhang" <[e-mail]>

I think the number may have to be the type of extended, otherwise
sprintf may not behave well ( but I am not a hundred percent sure).  You
could use one of the SANE functions: "num2str", which does a better job.
-----------------------------------------------------
From: [e-mail] (Kirk Swenson)

Make sure that the ANSI library and your application are compiled with all
of the same settings, specifically the options relating to compilation of
floating point numbers.  You probably will have to recompile the ANSI
library, which is explained in the manual.

-----------------------------------------------------
From: "Kerry Shetline" <[e-mail]>

> sprintf(aString,"%Lg",aNumber);

I think you need a capital G.

***** both "g" and "G" are valid and have slightly different
      behaviour
-----------------------------------------------------










Path: ucivax!gateway
From: [e-mail] (Mark Nagel)
Subject: ARCHIVE: CMIDI 2.1
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Reply-To: [e-mail]
Lines: 18
Date: 16 Apr 93 16:16:14 GMT

Date: Wed, 14 Apr 1993 15:48:29 -0800
From: Paul Ferguson <[e-mail]>
Subject: CMIDI 2.1 Submission

My CMIDI class library provides complete functionality for MIDI Manager
programming under TCL and is compatible with THINK C 5.0 and MIDI Manager
1.2 and 2.0.  It includes a detailed programmer's reference manual, an
example program demonstrating its use, and complete source code.

-- fergy

..........................................................................
Paul Ferguson                             Internet: [e-mail]
  Kaleida Developer Services             AppleLink: kaleida.dev
  Kaleida Labs, Inc. [phone]     CompuServe: 70441,3055
..........................................................................

[saved as: /mac/think-c/classes/cmidi-21.hqx; 256K]










Path: ucivax!gateway
From: [e-mail] (Brian Williams)
Subject: Printing
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 10
Date: 19 Apr 93 18:30:25 GMT


I am using TC 5.0 and need to print a file.   The file has been created
with ANSI file functions (fopen).  I would like to avoid using SFGetFile
to open the file for printing (The users will get a printout whether
they like it or not).

Any help would be appreciated.

Brian Williams
[e-mail]










Path: ucivax!gateway
From: [e-mail] (Randy Bradley)
Subject: Re:  Printing
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 1
Date: 20 Apr 93 13:43:30 GMT












Path: ucivax!gateway
From: [e-mail] (Randy Bradley)
Subject: Re:  Printing
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 2
Date: 20 Apr 93 13:46:42 GMT

d











Path: ucivax!gateway
From: [e-mail] (Christopher Evans)
Subject: Help wanted
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 26
Date: 21 Apr 93 14:29:51 GMT


MAC PROGRAMMERS IN THE NEW YORK AND BOSTON AREA:

Natural Intelligence, Inc. providers of a full range of computer
consulting services, has an immediate opening for a professional,
articulate Macintosh expert. We offer excellent pay, generous
benefits, and an attractive profit-sharing plan.

Natural Intelligence is a growing company with room for a highly
motivated individual. From the outset, this person must have the
skills, energy, and commitment to contribute to a team effort.

Candidates must have a strong working knowledge of many of the
following: 4th DIMENSION, MacToolbox, C, SQL, Sybase,
and/or Oracle.

Natural Intelligence is an equal opportunity employer.

Please send information to Natural Intelligence at:

e-mail: [e-mail]
fax:    [phone]
usps:   2067 Massachusetts Avenue
        Cambridge, MA 02140












Path: ucivax!gateway
From: [e-mail] (Jon Wiederspan)
Subject: C Pretty Printer
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 8
Date: 22 Apr 93 15:23:46 GMT

Is there a "pretty printer" for C code on the Mac?  I have Think C 5.0x but I
didn't see one in the software.  Specifically, I'm looking for one that will
allow me to set the fonts & styles for code vs. comment vs. keyword and print
function banners.  I tried "PrettyC 1.43" by Jeremy somebody, but it quits
every time I try to open a file (System 7.1 with Japanese extensions).

Thanks!
Jon Wiederspan   [e-mail]










Path: ucivax!gateway
From: [e-mail] (Robert Story)
Subject: porting from unix
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 15
Date: 23 Apr 93 02:16:10 GMT

is there a document somewhere that has hints/tips for porting other platforms
to the Mac?  I am trying to port GNU Zip with Think C 5.0.3.  I have the
compiler set to ANSI conformance, and 4 byte ints.  Right now, I am getting
errors on Mac includes.  ie, Memory.h gives me these errors :

- illegal type for variable
pascal Handle TempNewHandle(Size logicalSize,OSErr *resultCode)
    = {0x3F3C,0x001D,0xA88F};


- invalid declaration
typedef pascal long (*GrowZoneProcPtr)(Size cbNeeded);

rstory











Path: ucivax!gateway
From: [e-mail] (Rich Siegel)
Subject: Re:  porting from unix
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 9
Date: 23 Apr 93 03:41:06 GMT

The ANSI-conformant settings preclude use of Mac-specific (and non-
conformant) features such as 'pascal'-declared functions and inlines.
However, you can click the "ANSI" button, and then check the "THINK C"
extensions check box, and you'll be able to compile ANSI-conformant
programs and use the Mac interfaces for Mac-specific code.

BTW, 5.0.4 is the latest version.

R.










Path: ucivax!gateway
From: [e-mail] (Jim Lynch)
Subject: Re:  porting from unix
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 1
Date: 23 Apr 93 11:21:57 GMT

The person to ask about anything GNU is [e-mail].










Path: ucivax!gateway
From: [e-mail] (Timothy Murphy)
Subject: Re: porting from unix
Message-ID: <[e-mail]>
In-Reply-To: Robert Story's message of 23 Apr 93 02:16:10 GMT
Newsgroups: fa.think-c
Lines: 37
Date: 23 Apr 93 14:20:09 GMT

> is there a document somewhere that has hints/tips for porting other platforms
> to the Mac?  I am trying to port GNU Zip with Think C 5.0.3.  I have the
> compiler set to ANSI conformance, and 4 byte ints.  Right now, I am getting
> errors on Mac includes.  ie, Memory.h gives me these errors :
>
> - illegal type for variable
> pascal Handle TempNewHandle(Size logicalSize,OSErr *resultCode)
>     = {0x3F3C,0x001D,0xA88F};
>
>
> - invalid declaration
> typedef pascal long (*GrowZoneProcPtr)(Size cbNeeded);

I have compiled gzip using Think C without much difficulty.
The compiled program can be found at ftp.maths.tcd.ie
in pub/Mac/gzip.hqx .

The sources (or rather diffs from the official sources of gzip)
can be found in the directory /src/gnu/gzip-1.0.7/Mac .

I use a "Posix" library ThinkCPosix which contains some Unix functions
missing from the Think C library.
I will put this in pub/Mac/ThinkCPosix.

If un-gzipping text files gzipped on Unix,
you much give the switch '-a'.

I've been very impressed with both the compression and the speed of gzip.

Timothy Murphy

e-mail: [e-mail]
tel: [phone] (home/office)
     [phone] (university)
fax: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland











Path: ucivax!gateway
From: [e-mail]
Subject: Chaos Digest, #1.19
Message-ID: <[e-mail]>
Content-Type: text
Newsgroups: fa.think-c
Lines: 541
Date: 24 Apr 93 07:15:22 GMT

Chaos Digest               Lundi 19 Avril 1993          Volume 1 : Numero 19

       Editeur: Jean-Bernard Condat ([e-mail])
       Archiviste: Yves-Marie Crabbe
       Co-Redacteurs: Arnaud Bigare, Stephane Briere

TABLE DES MATIERES, #1.19 (19 Avril 1993)
File 1--Alertes aux fausses factures d'annuaires France Telecom
File 2--Le "Clipper Chip": rapide descriptif
File 3--Slide presente a la Maison Blanche durant le briefing
File 4--Clipper Chip et le FBI (reprints)
File 5--Piratage France Telecom par un technicien France Telecom

Chaos Digest is a weekly electronic journal/newsletter. Subscriptions are
available at no cost by sending a message to:
                [e-mail]
with a mail header or first line containing the following informations:
                    X-Mn-Admin: join CHAOS_DIGEST

The editors may be contacted by voice ([phone]), fax [phone])
or S-mail at: Jean-Bernard Condat, Chaos Computer Club France [CCCF], B.P.
155, 93404 St-Ouen Cedex, France.

Issues of ChaosD can also be found on some French BBS.  Back issues of
ChaosD can be found on the Internet as part of the Computer underground
Digest archives.  They're accessible using anonymous FTP from:

        * kragar.eff.org [192.88.144.4] in /pub/cud/chaos
        * uglymouse.css.itd.umich.edu [141.211.182.91] in /pub/CuD/chaos
        * halcyon.com [192.135.191.2] in /pub/mirror/cud/chaos
        * ftp.cic.net [192.131.22.2] in /e-serials/alphabetic/c/chaos-digest
        * ftp.ee.mu.oz.au [128.250.77.2] in /pub/text/CuD/chaos
        * nic.funet.fi [128.214.6.100] in /pub/doc/cud/chaos
        * orchid.csv.warwick.ac.uk [137.205.192.5] in /pub/cud/chaos

CHAOS DIGEST is an open forum dedicated to sharing French information among
computerists and to the presentation and debate of diverse views. ChaosD
material may be reprinted for non-profit as long as the source is cited.
Some authors do copyright their material, and they should be contacted for
reprint permission.  Readers are encouraged to submit reasoned articles in
French, English or German languages relating to computer culture and
telecommunications.  Articles are preferred to short responses.  Please
avoid quoting previous posts unless absolutely necessary.

DISCLAIMER: The views represented herein do not necessarily represent
            the views of the moderators. Chaos Digest contributors
            assume all responsibility for ensuring that articles
            submitted do not violate copyright protections.

----------------------------------------------------------------------

Date: Thu Apr 15 11:47:00 +0200 1993
From: [e-mail] (Stephane DUFOUR )
Subject: File 1--Alertes aux fausses factures d'annuaires France Telecom


     Depuis plus de deux ans, des vagues de pseudo-factures imitant les
factures de France Telecom, se repandent sur le territoire national.  Ces
documents constituent une double tromperie:

     * Ils se presentent d'une part comme des factures, alors qu'ils ne
sont censes etre qu'une offre d'abonnement a un service d'annuaire pour la
telecopie, le telex ou le Minitel.  Cette presentation visiblement destinee
a abuser les consommateurs est penalement reprehensible et confine a la
tentative d'escroquerie.

     * Ils imitent d'autre part d'une facon plus ou moins manifeste les
factures emises par France Telecom, tant en ce qui concerne le nom du
service (France service Minitel, France Telecopie) que la presentation
generale, le logo ou la couleur a dominante bleue.  Ceci constitue aussi
une infraction de contrefacon ou imitation illicite.

     Des l'apparition de ces fraudes, France Telecom a reagi en portant
plainte chaque fois qu'une nouvelle affaire apparaissait.  Il a mis en garde
tous ses abonnes individuellement contre les risques de confusion.  Il est
intervenu sur ce sujet a de nombreuses reprises dans les medias et continue
de la faire.  Une collaboration etroite a ete etablie avec le parquet de
Paris qui centralise les plaintes et coordonne les differentes enquetes.

     France Telecom transmet en particulierles nouveaux "modeles" de factures
des qu'ils lui sont signales.  A titre d'exemple, cette cooperation entre
la justice, France Telecom et la Poste a permis en un an d'intercepter sur
commission rogatoire pres de 350 000 plis avant leur distribution et de
bloquer, en liaison avec les banques de nombreux cheques.

     L'instruction judiciaire a ete rendue plus difficile par le caractere
international de la fraude qui affecte une bonne partie de l'Europe et
utilise l'Autriche et le Lichtenstein comme plaques tournantes.  Toutefois
plusieurs personnes devraient etre traduites devant le tribunal correction-
nel d'ici cet ete.

------------------------------

Date: Wed, 21 Apr 93 19:21:48 EDT
From: [e-mail] (Dorothy Denning )
Subject: File 2--Le "Clipper Chip": rapide descriptif
Repost from: RISKS Digest


                     THE CLIPPER CHIP: A TECHNICAL SUMMARY
                               Dorothy Denning
                           Revised, April 21, 1993

INTRODUCTION

On April 16, the President announced a new initiative that will bring
together the Federal Government and industry in a voluntary program
to provide secure communications while meeting the legitimate needs of
law enforcement.  At the heart of the plan is a new tamper-proof encryption
chip called the "Clipper Chip" together with a split-key approach to
escrowing keys.  Two escrow agencies are used, and the key parts from
both are needed to reconstruct a key.


CHIP CONTENTS

The Clipper Chip contains a classified single-key 64-bit block
encryption algorithm called "Skipjack."  The algorithm uses 80 bit keys
(compared with 56 for the DES) and has 32 rounds of scrambling
(compared with 16 for the DES).  It supports all 4 DES modes of
operation.  The algorithm takes 32 clock ticks, and in Electronic
Codebook (ECB) mode runs at 12 Mbits per second.

Each chip includes the following components:

   the Skipjack encryption algorithm
   F, an 80-bit family key that is common to all chips
   N, a 30-bit serial number (this length is subject to change)
   U, an 80-bit secret key that unlocks all messages encrypted with the chip

The chips are programmed by Mykotronx, Inc., which calls them the
"MYK-78."  The silicon is supplied by VLSI Technology Inc.  They are
implemented in 1 micron technology and will initially sell for about
$30 each in quantities of 10,000 or more.  The price should drop as the
technology is shrunk to .8 micron.


ENCRYPTING WITH THE CHIP

To see how the chip is used, imagine that it is embedded in the AT&T
telephone security device (as it will be).  Suppose I call someone and
we both have such a device.  After pushing a button to start a secure
conversation, my security device will negotiate an 80-bit session key K
with the device at the other end.  This key negotiation takes place
without the Clipper Chip.  In general, any method of key exchange can
be used such as the Diffie-Hellman public-key distribution method.

Once the session key K is established, the Clipper Chip is used to
encrypt the conversation or message stream M (digitized voice).  The
telephone security device feeds K and M into the chip to produce two
values:

   E[M; K], the encrypted message stream, and
   E[E[K; U] + N; F], a law enforcement field ,

which are transmitted over the telephone line.  The law enforcement
field thus contains the session key K encrypted under the unit key U
concatenated with the serial number N, all encrypted under the family
key F.  The law enforcement field is decrypted by law enforcement after
an authorized wiretap has been installed.

The ciphertext E[M; K] is decrypted by the receiver's device using the
session key:

        D[E[M; K]; K] = M .


CHIP PROGRAMMING AND ESCROW

All Clipper Chips are programmed inside a SCIF (Secure Compartmented
Information Facility), which is essentially a vault.  The SCIF contains
a laptop computer and equipment to program the chips.  About 300 chips
are programmed during a single session.  The SCIF is located at
Mykotronx.

At the beginning of a session, a trusted agent from each of the two key
escrow agencies enters the vault.  Agent 1 enters a secret, random
80-bit value S1 into the laptop and agent 2 enters a secret, random
80-bit value S2. These random values serve as seeds to generate unit
keys for a sequence of serial numbers.  Thus, the unit keys are a
function of 160 secret, random bits, where each agent knows only 80.

To generate the unit key for a serial number N, the 30-bit value N is
first padded with a fixed 34-bit block to produce a 64-bit block N1.
S1 and S2 are then used as keys to triple-encrypt N1, producing a
64-bit block R1:

        R1 = E[D[E[N1; S1]; S2]; S1] .

Similarly, N is padded with two other 34-bit blocks to produce N2 and
N3, and two additional 64-bit blocks R2 and R3 are computed:

        R2 = E[D[E[N2; S1]; S2]; S1]
        R3 = E[D[E[N3; S1]; S2]; S1] .

R1, R2, and R3 are then concatenated together, giving 192 bits. The
first 80 bits are assigned to U1 and the second 80 bits to U2.  The
rest are discarded.  The unit key U is the XOR of U1 and U2.  U1 and U2
are the key parts that are separately escrowed with the two escrow
agencies.

As a sequence of values for U1, U2, and U are generated, they are
written onto three separate floppy disks.  The first disk contains a
file for each serial number that contains the corresponding key part
U1.  The second disk is similar but contains the U2 values.  The third
disk contains the unit keys U.  Agent 1 takes the first disk and agent
2 takes the second disk.  Thus each agent walks away knowing
an 80-bit seed and the 80-bit key parts.  However, the agent does not
know the other 80 bits used to generate the keys or the other 80-bit
key parts.

The third disk is used to program the chips.  After the chips are
programmed, all information is discarded from the vault and the agents
leave.  The laptop may be destroyed for additional assurance that no
information is left behind.

The protocol may be changed slightly so that four people are in the
room instead of two.  The first two would provide the seeds S1 and S2,
and the second two (the escrow agents) would take the disks back to
the escrow agencies.

The escrow agencies have as yet to be determined, but they will not
be the NSA, CIA, FBI, or any other law enforcement agency.  One or
both may be independent from the government.


LAW ENFORCEMENT USE

When law enforcement has been authorized to tap an encrypted line, they
will first take the warrant to the service provider in order to get
access to the communications line.  Let us assume that the tap is in
place and that they have determined that the line is encrypted with the
Clipper Chip.  The law enforcement field is first decrypted with the
family key F, giving E[K; U] + N.  Documentation certifying that a tap
has been authorized for the party associated with serial number N is
then sent (e.g., via secure FAX) to each of the key escrow agents, who
return (e.g., also via secure FAX) U1 and U2.  U1 and U2 are XORed
together to produce the unit key U, and E[K; U] is decrypted to get the
session key K.  Finally the message stream is decrypted.  All this will
be accomplished through a special black box decoder.


CAPSTONE: THE NEXT GENERATION

A successor to the Clipper Chip, called "Capstone" by the government
and "MYK-80" by Mykotronx, has already been developed.  It will include
the Skipjack algorithm, the Digital Signature Standard (DSS), the
Secure Hash Algorithm (SHA), a method of key exchange, a fast
exponentiator, and a randomizer.  A prototoype will be available for
testing on April 22, and the chips are expected to be ready for
delivery in June or July.


ACKNOWLEDGMENT AND DISTRIBUTION NOTICE

This article is based on information provided by NSA, NIST, FBI, and
Mykotronx.  Permission to distribute this document is granted.

------------------------------

Date: Mon, 19 Apr 93 9:21:53 EDT
From: [e-mail] (Clipper Chip Announcement )
Subject: File 3--Slide presente a la Maison Blanche durant le briefing

Note:     The following material was handed out a press briefing on the
          Clipper Chip on 4/16.

                        Chip Operation

                           Microchip
User's Message      +----------------------+
------------------> |                      |      1.  Message encrypted
                    | Encryption Algorithm |          with user's key
                    |                      |
                    | Serial #             |      2.  User's key encrypted
                    |                      |-->       with chip unique key
                    | Chip Unique Key      |
User's Encryption   |                      |      3.  Serial # encrypted
Key                 | Chip Family Key      |          with chip family key
------------------> |                      |
                    |                      |
                    +----------------------+


              For Law Enforcement to Read a Suspect's Message

1. Need to obtain court authorized warrant to tap the suspect's telephone;

2. Record encrypted message;

3. Use chip family key to decrypt chip serial number;

4. Take this serial number *and* court order to custodians of disks A and B;

5. Add the A and B components for that serial number = the chip
   unique key for the suspect user;

6. Use this key to decrypt the user's message key for
   this recorded message;

7. Finally, use this message key to decrypt the recorded message.

------------------------------

Date: Mon Apr 19 12:58:44 -0400 1993
From: [e-mail] (Paul Rutkovsky )
Subject: File 4--Clipper Chip et le FBI (reprints)
Copyrights: Warren Publishing, Inc. & San Jose Mercury News, 1993


GOVT. WEIGHS IN ON PRIVACY-VS.-ENCRYPTION DEBATE,  WITH ITS OWN TECHNOL OGY

Communications Daily   April 19, 1993   p. N/A
ISSN: 0277-0679

    Clinton   Administration   Fri.  announced  sweeping  policy  directive
designed   to  protect  privacy  of  voice  and  data  transmissions  using
govt.-developed encryption technology that ensures law enforcement agencies
will  have  ability  to  eavesdrop.  Encyrption is  achieved through use of
"Clipper    Chip  "  that  will  be  built  into telephones, computers, fax
machines.  Although  govt.  will  adopt  new  chip  as its standard, use in
private sector will be on voluntary basis.

    AT&T  Fri.  became  first  company  to  announce  publicly  support  of
 Clipper    Chip  .  "We  believe  it  will  give our customers far greater
protection in defeating hackers or eavesdroppers in attempting to intercept
a  call,"  said  AT&T Vp Secure Communications Systems Edward Hickey. Govt.
already has purchased some evaluation units from AT&T with  Clipper   Chip
installed,  said  Raymond  Kramer,  acting  dir.  of  National Institute of
Standards  &  Technology  (NIST).  Govt. expects to purchase "well over the
thousands"  of  such   Clipper   Chip  units, he said, but he couldn't give
figures  for  how many it might buy from AT&T. AT&T spokesman said products
with   Clipper    Chip   included  will  be  available  commercially in 2nd
quarter.

    President  Clinton Thurs. signed Top Secret National Security Directive
outlining  details  of  privacy  and  encryption policy review. Review will
bring  together  industry  and  govt.  experts  under direction of National
Security Council in attempt to resolve long-running controversy on right of
businesses  and  citizens  to  protect all forms of communication and govt.
right to conduct lawful investigations. Review will take 3-4 months, NIST's
Kramer said.

    Law  enforcement  agencies  are  concerned  about  rising popularity of
digital   encryption   methods.  Multinational  businesses,  worried  about
economic  espionage,  increasingly  are incorporating encryption technology
for  all  communications.  Law  enforcement  agencies  have  voiced growing
concern  that if they don't move quickly to enact laws assuring them access
to   encrypted   and  digital  communications,  they  will  be  at  decided
disadvantage in attempting to thwart  criminal acts.   FBI  spokesman James
Kallstrom acknowledged that "not many" criminals today are using encryption
to  skirt  law,  but  putting  methods  in  place  now  to  assure means of
intercepting such communications "is vital" to law enforcement's mission.

    Encryption  program  will  be  available  to  any  vendor that wants to
manufacture  chips,  Kramer  said.  However,  company  that  developed  and
designed  chip  under  sole-source  contract  from National Security Agency
(NSA)  --  Mykotronx,  Torrance,  Cal.  -- has solid lead on market. Kramer
acknowledged   job   was   handed   to  it  with  NSA's  full  approval  of
noncompetitive  bid  contract.  He defended noncompetition aspect: "We went
out  and  found the only company capable of delivering this technology." He
said  govt.  has been using  Clipper   Chip  technology for "a while now in
classified  applications,"  but declined to say how long it had been in use
before  White   House  announcement.

    Each  chip will have 3 unique "keys" issued to it. When manufactured, 2
of  those  keys  will be sent to govt. and will be held by "escrow agents."
For  law  enforcement  agency to be able descramble transmissions, it first
must  get  court order that allows keys held in escrow to be released. Only
when  those keys are used in tandem can law enforcement agencies unscramble
codes and listen in on conversations. Attorney Gen.'s office will "make all
arrangements with appropriate entities to hold keys,"  White   House  said.
Those escrow keys could be held by private organizations, govt. agencies or
others,  Kramer  said.  But  only  2  entities  will  be chosen and will be
responsible  for  administering  data  base  that will store keys. Attorney
Gen.'s  office is expected to select escrow key holders "within a couple of
weeks," Kramer said.

    Plan  already  is  drawing fire from civil liberties groups and privacy
advocates.  Electronic Frontier Foundation (EFF) said  White   House  acted
"before  any  public  comment  or  discussion  has  been  allowed." It said
Administration  will  use  "its  leverage  to  get  all telephone equipment
vendors  to adopt" technology. EFF criticized govt.'s sole-source contract,
saying there may be other companies that have better encryption technology,
and  because  encryption  algorithm is classified, it can't be tested. "The
public will only have confidence in the security of a standard that is open
to  independent,  expert scrutiny," EFF said. Privacy experts are concerned
that  because   Clipper    Chip  was developed under NSA contract, it might
have "backdoor" known only to NSA that would allow agency to crack code and
bypass  court  order. Kramer disagreed: "There is positively no backdoor to
this technology."

    Because  use  of  Clipper   Chip  is entirely voluntary, businesses and
private  users  -- including criminals -- are free to choose other means of
encryption,  leaving  govt.  and law enforcement agencies with dilemma they
now  face.    FBI  's  Kallstrom  acknowledged criminals still could thwart
investigations  if  they  used  non- Clipper    Chip   products,  "but most
criminals aren't so smart."

    Ability  of  govt.   to  eavesdrop on  Clipper   Chip -equipped devices
still  doesn't  solve  broader  problem:  Ability  to wiretap conversations
moving  across  digital  telecommunications  lines.  That  problem is being
addressed  separately  by  FBI 's controversial digital wiretap legislation
that has failed to find congressional sponsor and is languishing in Justice
Dept., waiting for support of Attorney Gen.

+++++

U.S. SCHEME TO EAVESDROP ELECTRONICALLY RAISES CONCERNS CIVIL LIBERTARIANS,
INDUSTRY GROUP WANT PUBLIC INPUT INTO 'KEY' PLAN
San Jose Mercury News (SJ) - Saturday, April 17, 1993
By: RORY J. O'CONNOR, Mercury News Staff Writer
Edition: Morning Final  Section: Business  Page: 11D

Civil  libertarians  and  a  major  computer industry group raised concerns
Friday about how much protection a Clinton administration plan would afford
private   electronic  communications,  from  cellular  telephone  calls  to
computer data.

  The  administration Friday said it would begin using technology developed
by  the  government's  National  Institute  of  Standards and Technology to
balance  two  competing  interests:  the  desire  of citizens to keep their
conversations  private and the need for law enforcement agencies to monitor
those conversations after getting a court order.

The  technology  that   enables this is a computer chip called the  Clipper
Chip   that  scrambles a  telephone call or computer message using a secret
algorithm, or formula.

  But  each  chip also comes with a pair of electronic "keys" that could be
used  by law enforcement agencies to decipher the secret messages generated
by the chip.

  The Clinton proposal calls for one key to be held by each of two separate
"trusted" third parties, who would release them to law enforcement agencies
that  obtained  legal  authority to intercept the communications. Both keys
would be needed to decipher a message.

  The  Electronic  Frontier  Foundation,  a  not-for-profit civil liberties
group,  praised  the  administration  for  considering  the  issue.  But it
criticized the lack of public input into the plan.

  "They've announced a big inquiry with public input, but they've reached a
conclusion before they started," said Daniel J. Weitzner, staff counsel for
the Washington-based foundation.

  Although  the  administration's  plan calls only for equipping government
telephones  with  the  security devices, some groups are concerned the plan
might  become  a standard for all manner of electronic communication before
the public has a chance to debate its merits.

  "I  don't  want to sound too stridently opposed to this," said Ken Wasch,
executive   director  of  the  Software  Publishers  Association  (SPA)  in
Washington. "But... we feel blindsided."

  The  SPA  was discussing data security issues with Clinton administration
officials  but  had  not  expected any  White   House  action until August,
said Ilene Rosenthal, general counsel.

  Besides the lack of initial hearings, both groups said they had two major
concerns about the Clinton plan:

  (box)  Because  the  algorithm  itself  is  secret,  the groups say it is
impossible  for the public to discern if it is truly secure. Users can't be
certain  government  spy  agencies  have  not  hidden  a "back door" in the
software that will allow them to read anything they want.

  "So  far there hasn't been a credible explanation about why the algorithm
has to be secret," Weitzner said.

  (box)  The  administration  hasn't decided who will be the escrow agents,
and  it  seems  unlikely  any  government agency, corporate entity or other
organization would be deemed trustworthy by every user.

  Even  assuming  all  concerned  can  agree  on  who will hold them, civil
libertarians  are  concerned  that  the  keys,  by  giving  law enforcement
agencies access to individuals' private communications, might pose a threat
to constitutional protections against self-incrimination.

   Washington sources who requested anonymity suggested the  White    House
might  have  drafted  its  plan quickly because of concern over sales of an
AT&T  device  that  encrypts  phone  calls  using  an  older standard, Data
Encryption  Standard. The sources said law enforcement officials feared the
device  would  create  an explosion in secured telephone traffic that would
severely hamper their efforts to wiretap calls.

  American Telephone & Telegraph announced Friday it would adapt the $1,200
product,  called the Telephone Security Device, to use the  Clipper    Chip
by  the  end  of  this  fiscal  quarter. AT&T makes a related device, which
encrypts  voice and computer data transmissions, that could be converted to
the Clipper technology, said spokesman Bill Jones.

  Jones  said  he  wasn't  aware  of any concern by the government over the
current  model  of  the  Telephone  Security Device, which has been sold to
government and business customers.

  At least one company was quite pleased with the plan: San Jose chip maker
VLSI  Technology,  which  will  manufacture  the   Clipper    chips   for a
Torrance company that is selling them to the government and to AT&T.

  VLSI,  which  invented  a  manufacturing method the company said makes it
difficult  to "reverse engineer" the chip or discern the encryption scheme,
expects  to  make  $50  million in the next three years selling the device,
said Jeff Hendy, director of new product marketing for the company.

------------------------------

Date: Thu Apr 15 11:47:00 +0200 1993
From: createuraltern.com (Fabien Pigere )
Subject: File 5--Piratage France Telecom par un technicien France Telecom
Copyright: Elsevier Science Publishers Ltd., 1992

ADDING TO CHAOS
Network Monitor      March, 1992
ISSN: 0953-8402               WORD COUNT: 121
PUBLISHER:  Elsevier Advanced Technology Publications

France  Telecom was in the news again recently after a technician was found
guilty  of  aiding  hackers  to  gain information about using international
network connections.

The  technician  worked for Intelcom France, an FT subsidiary which manages
the international transit node (NTI) for France Telecom networks.

According  to  the  police  the technician "played a determine role" in the
leak of NTI access codes notably to the Chaos Computer Club France.

Jean-Bernard Condat of the CCCF denied the accusation that his organization
which he says specializes in the security of information systems,  received
the access codes from the technician.

The  Chaos  Computer  Club  began life in Germany and has played a twilight
role,  half  supporting hackers and half finding security loopholes ignored
or hidden by suppliers and operations.

INDUSTRY:  Telecommunications (TL)

------------------------------

End of Chaos Digest #1.19
************************************










Path: ucivax!gateway
From: [e-mail] (Sigurdur Darri)
Subject: xtnd system
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
X-Charset: ASCII
Lines: 28
Date: 27 Apr 93 13:01:46 GMT
X-Char-Esc: 29

   I'm using the XTND system to process a file and hyphnate it. Recently
I discovered strange bugs occuring in microsoft word files, which seemed
to happen at most bizarre times like f.inst. if I had a paragraph with a
length
over 150 bytes and a picture after that, then the picture would vanish.
After heavy use of the think c debugger and much coffee the simple solution
appeared to be that the field totalCharCount in the xtnd system which
usually
doesnt matter is needed for all word files (not just word 3.0 as the
comments
in the header file say) with strange things happening if it is not valid.
However I have some difficulties in knowing the excact size of the file
when I create it. Of course I could create temporary files and use them to
find the target text length but that would be rather timeconsuming.

So.. does anyone have any experience with the word translator? Do you know
if there is a way to use it without having to set this totalcharcount, or
what limits there are on the value of it being the excactly right one?

thanks,

 Sigurdur.
---
  _/_/  Sigurdur Darri Skulason         email:     [e-mail]
 _/_/   Softis hf.                                 [e-mail]
_/_/    Macintosh Division                         [e-mail]
---                                     Applelink: ICE0008











Path: ucivax!gateway
From: [e-mail] (Igor Livshits)
Subject: Is main() required in all code resourcves?
X-Sender: [e-mail]
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 12
Date: 27 Apr 93 17:10:50 GMT

Howdy,

I am trying to write a custom code resource (a plug-in module) which will
be nothing but a set of functions called by the main application.  Why
would I need need a main() for  such a code resource?  The THINK C manual
seems to imply that I need a main90 for every such code resource.

Thank you for your help,
Igor
_____
NCSA-UIUC,  e:[e-mail],  p:[phone]











Path: ucivax!gateway
From: [e-mail] (inei)
Subject: How to find folder name after FindFolder()?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 15
Date: 27 Apr 93 17:52:14 GMT


Someone please help me before I tear all my hair out!

I am trying to get the pathname of the System file.

I've used FindFolder() which dutifully gives me the volume reference
number and the directory ID of the System Folder.  Now I want to
OpenResFile() the System file, so I would like to get the pathname
of the System file.  Given only the System Folder's volume reference
number and directory ID, how do I find out the system folder's name?

Mail:  Nick Nei, Computing Science Dept.,
       Glasgow Univ., 17 Lilybank Gardens,
       Glasgow G12 8QQ, UK.  Tel: [phone] x 5457
ARPA:  [e-mail] USENET: [e-mail]










Path: ucivax!gateway
From: [e-mail] (Pete Gontier)
Subject: Re: Is main() required in all code resourcves?
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>; from "Igor Livshits" at Apr 27, 93 5:10 pm
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: fa.think-c
Lines: 23
Date: 27 Apr 93 19:19:20 GMT

> I am trying to write a custom code resource (a plug-in module) which will
> be nothing but a set of functions called by the main application.  Why
> would I need need a main() for  such a code resource?  The THINK C manual
> seems to imply that I need a main90 for every such code resource.

In general, you don't *need* a main to link. For example, a Windows
DLL is quite happy without one. An MPW code resource is, too, although
you do still have to specify the name of the primary entry point.

The trick here is that the THINK C linker expects there to be a
main.  The various pieces of startup code produced by THINK C each do
a subroutine call to main. Whether that is good or bad is left as an
exercise.

What *you* might find main useful for is setting up a block full of
function addresses for the benefit of the caller. You'll have to
figure out some way to do this to achieve what you want anyway, and
in many ways doing this sort of work in main is a lot easier than
alternatives like parsing the link map. And more resistant to changes
in the complier, too.

--
 Pete Gontier // EC Technology // [e-mail]










Path: ucivax!gateway
From: [e-mail] (Robert Mah)
Subject: Re: Is main() required in all code resourcves?
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Newsgroups: fa.think-c
Lines: 24
Date: 27 Apr 93 22:44:23 GMT

Igor,

On 27 Apr 1993, Igor Livshits wrote:

> I am trying to write a custom code resource (a plug-in module) which will
> be nothing but a set of functions called by the main application.  Why
> would I need need a main() for  such a code resource?

main() is used as the entry point.  The linker makes sure that main() is
called before any other function.  If this wasn't the case, you'd have
to worry about the order of the functions in your project -- not real fun.

BTW, what program is the plug-in for?  The "host" software determines
how you should declare your main().

Cheers,
Rob

[----------------------------------------------------------------------]
[ Robert S. Mah   | Voice: 212-947-6507   | "Every day an adventure,   ]
[ One Step Beyond | EMail: [e-mail] |  every moment a challenge" ]
[----------------------------------------------------------------------]












Path: ucivax!gateway
From: [e-mail] (Robert Mah)
Subject: Re: How to find folder name after FindFolder()?
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Newsgroups: fa.think-c
Lines: 25
Date: 27 Apr 93 22:47:09 GMT

Nick,

On 27 Apr 1993, inei wrote:

> I've used FindFolder() which dutifully gives me the volume reference
> number and the directory ID of the System Folder.  Now I want to
> OpenResFile() the System file, so I would like to get the pathname
> of the System file.  Given only the System Folder's volume reference
> number and directory ID, how do I find out the system folder's name?

You can use HOpenResFile() instead of OpenResFile() which accepts a dirID,
a volume refnum and the filename.

However, if you still need to find the path, there's a code snippet from
DTS that can be found via anon ftp on ftp.apple.com that does it.

Cheers,
Rob

[----------------------------------------------------------------------]
[ Robert S. Mah   | Voice: 212-947-6507   | "Every day an adventure,   ]
[ One Step Beyond | EMail: [e-mail] |  every moment a challenge" ]
[----------------------------------------------------------------------]












Path: ucivax!gateway
From: [e-mail] (Igor Livshits)
Subject: Re: Is main() required in all code resourcves?
X-Sender: [e-mail]
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 38
Date: 27 Apr 93 23:01:03 GMT

Thank you to everyone who responded.  Sorry, Pete, you'll get two copies fo
this...

I think my confusion stems from the fact that MPW does not require this and
that some sample MPW code that I am trying to port to THINK C refuses to
work without a main().

I am trying to write a fader for the free screen saver Dark Side of the
Mac.  The example fader code does not have a main.  I believe the MPW
compiler assumes that the first function (no mattert the name) is the entry
point.  As such, can I take the MPW source, rename the first entry function
to main() and live happily ever after?

From the makefile:
"{OutputDir}"Invert ff "{ObjDir}"Invert.c.o "{ObjDir}"Fader.c.o
        Echo "Linking Invert"
        Link {LinkOptions} -o {Targ} d
        -m FaderEntry d
        -rt FADE=128 d
        -sg Fader  d
        "{ObjDir}Fader.c.o" d
        "{ObjDir}Invert.c.o"  d
        "{Libraries}"Runtime.o
        SetFile {Targ} -t 'Dark' -c 'DSOM'

Is the -m line the one that designates the first function?


BTW, if anyone has Dark Side fader example code in the THINK C dialect they
are willing to share, it would make me ecstatic.

I should probably talk to Tom Dowdy about this anyway...

Again, thanks for your input;
igor
_____
NCSA-UIUC,  e:[e-mail],  p:[phone]











Path: ucivax!gateway
From: [e-mail] (Ken B Kirksey)
Subject: SANE Strangeness?
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 49
Date: 29 Apr 93 20:32:40 GMT


Got a real headscratcher here. Well, it's a headscratcher to me;  I'm
sure one of you Think gurus out there will know what the problem is right
off. :-)

I just got the demo version of Inside Out II yesterday and I was having a
heck of time getting the demo program to compile.  I was getting the error

      "Second argument to function _elems1 does not match prototype."

on the line

      dh = 200 + 110 * sin (lineAng * 0.01745); /*</360 * 29 = RAD*/

where dh is a double and lineAng is a short.

I did some digging and found the SANE defintion of sine in SANE.h as

        #define sin(x)  _elems1(FSINX, x)

and _elems1 in sane4.c as

        _elems1(short op, extended x)

So it's complaining that the argument to the sin call (lineAng * 0.0175)
isn't of type extended (a SANE type?).  I know nothing of SANE, so I really
don't know what's going on here.  Can someone tell my why it's griping about
this.  The tech support guy at Sierra told me that they've gotten it to
compile with no problem.  I could only get it to compile when I commented out
the #include <SANE.h> line.  It compiled and ran fine when I did that.

FYI, it give the same error whether or not "Strict prototype enforcement"
is checked.  I had to turn off "check pointer types" because it really choked on
compile with that one.  This is definitely not ANSI conformant code. :-(

Many thanks in advance.


                          Ken

+------------------------+--------------------------------------------------+
| Ken Kirksey            | Someone who actually understands and generates   |
| Mac Guru & Developer   | unique JCL is regarded with the mixed respect    |
| [e-mail] | one give to someone who memorizes the phone book.|
|                        |                        - Eric Raymond            |
+------------------------+--------------------------------------------------+
| PGP 2.0 Key available via finger or keyserver.                            |
+---------------------------------------------------------------------------+











Path: ucivax!gateway
From: [e-mail] (Andrew McAllister)
Subject: curses, curses, curses.h,curses.c
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 14
Date: 30 Apr 93 03:18:52 GMT

Sorry about all the cursing on the net :), but does anybody know what this
curses.h and curses.c stuff is? I've got a bunch of source code that is
supposed to compile on a unix machine with the curses libraries. Well,
since Think C has a unix lib and is generally the best compiler for the
Mac, I thought I'd try to compile said code. But curses, lots of errors.

Here's what I'm looking for: Has anyone implemented the curses libraries
for the mac? I think they are designed to do terminal I/O on stupid terminals,
like the console in Think C. I know the console can do some cool stuff, like
clearing the screen, positioning the cursor etc. How do these functions
relate to the curses libs? Yikes! I don't really have access to a unix box
so I can't really do any testing or look at the curses headers etc.
Help???!??
andy     [e-mail]










Path: ucivax!gateway
From: [e-mail] (Tomaso Paoletti 345392/IL)
Subject: request of submission
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 8
Date: 30 Apr 93 12:09:20 GMT

I would like to submit to the Think-C mailing list
with a different e-mail address:

    [e-mail]

Tomaso Paoletti, [e-mail]

        Thanks in advance










Path: ucivax!gateway
From: [e-mail] (Igor Livshits)
Subject: BackgroundOnly and the debugger
X-Sender: [e-mail]
Message-ID: <[e-mail]>
Newsgroups: fa.think-c
Lines: 16
Date: 30 Apr 93 19:36:11 GMT

Howdy,

Am I correct in assuming that I cannot use the Think C Debugger with
background-only applications?  If I can, please tell me how.

I have written a bg-only application that seems to work when a stand-alone.
 When I try to run it as a project with the Debugger, the process register
under the Aplication menu (it should not), and when I quit it leaves a
ghost.  The Finder promptly crashes after the bg-only app is terminated in
the latter case.

Thanks for your help,
igor
_____
NCSA-UIUC,  e:[e-mail],  p:[phone]